Individual skill

user-spec-planning

Plans a feature, bug fix, or refactor as work/{feature}/user-spec.md through an adaptive interview, code research, and validation before implementation. Use whenever requirements should be agreed before coding, including thinking a feature through, describing what it must do, resuming an existing spec, and "/new-user-spec".

skills/user-spec-planning/SKILL.md

Read pinned source

Source commit ca44595f459eb84086cec8ed04d47f57bab945f3

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Local scripts
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 303
Repository last updated: Oct 21, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 10,660 bytes
assets/decisions.md.templateasset · 401 bytes
assets/interview.yml.templateasset · 3,356 bytes
assets/user-spec.md.templateasset · 2,499 bytes
references/splitting-user-specs.mddoc · 1,699 bytes
scripts/init-feature-folder.shruns · 2,532 bytes

Read excerpt


# User Spec Planning

Thorough adaptive interview → codebase research → completeness review → user-spec.md → three-lane
validation → user approval. Output: `work/{feature}/user-spec.md` with status `approved`.

## Interview Style

Conduct the interview in the language the user writes in. Be an engaged co-thinker: propose
solutions, challenge weak answers with concrete examples or code evidence, and keep interviewing
until the applicable requirements are understood.

- Ask 3–4 questions per batch and run as many batches as needed.
- Save every question and answer verbatim after each user response.
- Give one substantive challenge to a weak or unclear answer, then accept a supported answer and