to-spec

This skill takes the current conversation context and produces a task spec from a completed, user-confirmed grill-me discussion. Do NOT interview the user; just synthesize what you already know.

Do not use this skill as a general-purpose spec writer.

Preconditions

The current conversation must contain all of the following:

• A completed grill-me discussion about a software feature.
• The user's explicit confirmation that the shared-understanding recap is correct.
• No open question that would block implementation or acceptance, unless the user has explicitly accepted the risk.

If a precondition is missing, do not create a Ready spec, invent requirements, or begin another interview. State the missing prerequisite and direct the user back to grill-me.

Process

1. Explore the repository only when needed to verify vocabulary or a fact already relevant to the confirmed discussion. If a discovered contradiction would change the requirement or acceptance criteria, stop and return it to the user as a decision. Do not silently resolve it.

2. Create docs/specs/ at the repository root if it does not exist. Write the task spec to docs/specs/<feature-slug>.md, using a short kebab-case slug derived from the feature name.