A scoped edit to specs/requirements/prd.md. The instruction names the scope —
a feature to add, an actor to add, a feature to deepen, or the open questions
to resolve. Scope is the contract: sections the scope doesn't touch stay
byte-identical, and story numbers only ever append (they are permanent —
designs, criteria, and tasks cite them).
The PRD's shape is defined by the start skill's contract — load
loadSkillReference("start", "references/prd-contract.md") before writing.
The grilling skill owns the question mechanics for every branch below.
Add a feature
Run a short scoped interview (one form: what the feature does, for whom, and any policy it implies — skip what the instruction already says). Then:
- append the feature's stories with fresh numbers,
- write or extend
specs/requirements/features/<slug>.mdwith the depth, - place the new stories in Phasing: default them to the next unshipped phase and say so — pull them into a phase already being built only when the user explicitly asks,
- record any new product decisions (org defaults answer silently, as ever).
Done when every new story has a number, a phase, and an actor the Actors section defines.
Add an actor
Define the actor in Actors (product-level: name + what they can broadly see/do). Add or amend only the stories the instruction implies for them.
Go deeper on a feature
Expand specs/requirements/features/<slug>.md — interview for the missing
depth, then write it there. The PRD body gains at most new story lines the
depth surfaced; everything else lands in the feature file.
Resolve open questions
Walk the Open Questions list, one ask_question each. Two exits per
question:
- Answered — the answer moves to the section it belongs in (a decision, a story, a phase) and the question is removed.
- Deferred — the user says later: mark it "deferred — does not block design" and leave it in place.
Done when no question is left in the undecided state.
Close
Summarize exactly what changed — new story numbers, phases touched, questions resolved or deferred — in a few lines. The rest of the flow (design, build) stays untouched by this skill.