Write plans, source-of-truth documents and decision records that can be proven stale, superseded without deletion, and told apart from one another.
Plugin spec-authoring from marketplace modootoday in modootoday/marketplace. Commands read from the repo's manifest — 23 days ago.
adr-authoringWrite an architecture decision record (ADR) so a later reader can tell whether it still applies, including what was rejected and what would reverse it. Use when the user asks for an ADR or a decision record, or when a choice closes off alternatives or is expensive to undo. Not for plans still under
agent-plan-extractRecover a plan document that a read-only planning subagent returned only inside its final report, verbatim from the session transcript JSONL, save it under the project's plans directory with its naming convention, and diff it against the report to prove nothing was paraphrased. Use when a subagent o
plan-authoringWrite a plan document that states what is proposed, what was measured, and what is still unverified, and that can be superseded without being deleted. Use when starting multi-step work or recording an investigation.
sot-authoringWrite a source-of-truth, rule or convention document that can be proven stale, by pairing every rule with a command that checks it. Use when the user asks to document a rule, an invariant or a coding convention, or to write a source-of-truth document that later work must not quietly contradict.
/spec-authoring:adrStart a decision record — what was chosen, what was rejected and why, and what would reverse it.
/spec-authoring:planStart a plan document — a proposal that states what is measured, what is assumed, and how each phase is undone.
/spec-authoring:sotStart a source-of-truth document — an invariant paired with a command that proves it is still true.
Your own Naver blog, Place, Smart Store, shopping, search ad and news comment data read through the datalab.tools browser extension, plus card news, short-form video, tutorial posts and social copy built in its editors, with no invented numbers and no change made without asking.
31 skills
Numbers that mean what they say: ClickHouse SQL that reads the key and deduplicates correctly, Naver trend data read as ratios, metrics defined once, experiments designed before launch, retention read by cohort, and open survey responses grouped with every response id kept.
16 skills
Reading passages that hit a measured grade level, language drills, and teacher-side checks for coverage, answer keys, lesson timing, study calendars and rule-valid puzzles, with the numbers and logs shown.
14 skills
Growth and community work: store listings written for the people searching that store, Discord servers run with structure and consistent moderation, newsletters readers open and finish, a month of social posts a small team can ship, launch emails that lead with what changed, and sites submitted to Google, Naver and IndexNow engines from a pipeline.
13 skills
Early product-planning steps done carefully: spar on an idea, frame the problem behind a request, synthesize feedback without overstating it, rank a backlog while saying where the ranking is fragile, write a Korean PRD with testable acceptance criteria, and put a decision on one page with the recommendation first.
13 skills
Korean content that reads well and stays true: product copy fixed to the Toss writing principles, Naver blog posts planned for search, persona tone measured with markers, and ghostwriting that never invents the author's facts.
11 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.