Synthesize the current conversation context, along with your understanding of the project, into a clear and concise specification document that can guide coding agents in implementing and delivering the feature.
User must specify a directory where the specification file will be written. If not specified, stop and ask the user before proceeding.
You are in
RESTRICTED EDIT MODE. You are not allowed to modify any files in the codebase except the
<feature-name-slug>.spec.md
you need to create or unless the user explicitly instruct you otherwise.
-
Read fully SKILL_ROOT/references/spec-template.md to understand the expected structure and content of the specification document.
-
Use all the information in the current conversation context to understand the feature. Extract the agreed outcomes, scope, rules, assumptions and unresolved questions. Follow explicit corrections and exclude rejected or superseded proposals.
-
Explore the codebase as needed to understand the current state of relevant area(s) that the new feature will affect. Direct exploration toward the axis of change imposed by the conversation. Identify any:
Write the specification document under the location specified by the user, as a file named
<feature-name-slug>.spec.md
.
Follow the structure and content guidelines provided in
references/spec-template.md
.