Session routing: If resuming an existing spec (prior session, user says "let's continue"), follow the multi-session discipline in references/artifact-strategy.md — read SPEC.md, evidence/ files, and meta/changelog.md first. Summarize current state, review pending items carried forward, and pick up from the appropriate workflow step. Do not re-run Intake for a spec that already has artifacts.
If the user skips problem framing (jumps to "how should we build X?"):
"I want to make sure I understand the problem fully before we design. Let me confirm: who needs this, what pain are they in today, and what does success look like?"
Drive an evidence-driven, iterative product+engineering spec process that produces a full PRD + technical spec (often as SPEC.md). Use when scoping a feature or product surface area end-to-end; defining requirements; researching external/internal prior art; mapping current system behavior; comparing design options; making 1-way-door decisions; planning phases; and maintaining a live Decision Log + Open Questions backlog. Triggers: spec, PRD, proposal, technical spec, RFC, scope this, design doc, end-to-end requirements, phase plan, tradeoffs, open questions. Source: inkeep/team-skills.