| name | new-spec |
| description | Scaffold a spec triplet (spec.md / plan.md / context.md) under specs/YYYYMMDD-<name>/ before starting a non-trivial piece of work. Use when a task spans multiple modules / several commits / a new ADR, or when the user says "new spec", "์คํ ๋ง๋ค์ด", "plan this out", "spec this", "๊ธฐํ๋ถํฐ". |
| argument-hint | <name> |
| allowed-tools | Bash, Read, Edit |
new-spec
Structure non-trivial work before coding โ the spec is what keeps the work
grounded on the original ask (this is where reliability comes from, not from a
measurement system).
- Decide if a spec is warranted. Yes if the task touches โฅ2 modules / areas,
needs โฅ3 commits, introduces a new ADR, or is forward-only. Skip it for
small work (single file, doc-only, a follow-up) โ spec ceremony on tiny tasks
is net-negative.
- Scaffold: run
bash "${CLAUDE_PLUGIN_ROOT}/skills/new-spec/new-spec.sh" "<name>" from the
repo root. It creates specs/<date>-<slug>/{spec,plan,context}.md and prints
the directory.
- Fill, in order:
spec.md (the original ask verbatim + acceptance),
plan.md (dependency-ordered tasks), then load the tasks and surface N/M
as you work. A "done" tone before all plan tasks are consumed is not allowed.
context.md ## 0. Resume here โ write it with /harness-kit:handoff at
a stopping point; a fresh session resumes from it with /harness-kit:pickup.
