Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From specclaw
Interactively co-author a spec.md for an approved proposal using structured brainstorming techniques (5 Whys, JTBD, Inversion, Pre-mortem, MoSCoW). Use when you want a dialogue-driven spec instead of a single-shot plan.
How this skill is triggered — by the user, by Claude, or both
Slash command
/specclaw:author-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Interactively author spec.md for an approved proposal.
specclaw-validate-change .specclaw <change> plan. If it fails (typically: proposal.md missing), report the missing prerequisite and stop..specclaw/changes/<change>/spec.md already exists, show the user the first few lines and ask whether to overwrite. Default is no — abort if the user does not explicitly confirm overwrite.spec-author subagent via the Agent tool with subagent_type: "spec-author" and a prompt instructing it to author the spec for <change>. The agent reads proposal.md and writes spec.md itself; do not wrap the dialogue in this skill.specclaw-update-status .specclaw.github.sync: true in config.yaml): specclaw-gh-sync update .specclaw <change> to refresh the issue with the new spec.azdo.boards.sync: true): specclaw-azdo-issue update .specclaw <change>.Do not proceed to /specclaw:plan automatically. After spec.md is written, the user can run /specclaw:plan <change> (which will use the freshly-authored spec.md and generate design.md + tasks.md) when ready.
npx claudepluginhub chan4lk/specclaw --plugin specclawGenerates spec, design, and ordered task list from an approved proposal by analyzing the codebase and project context. Run after /specclaw:propose, before /specclaw:build.
Creates or updates SPEC.md documents from requirements, notes, or interview output, structuring into sections for goals, design, edge cases, security, testing, and success criteria. Use for feature specs.
Turns vague feature ideas into structured, agreed-upon specification documents through relentless questioning across nine dimensions. Produces persisted specs with acceptance criteria for planning and implementation.