spec

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?"

推動證據驅動、迭代的產品+工程規格流程，產生完整的 PRD + 技術規格（通常為 SPEC.md）。在端到端地確定功能或產品表面積範圍時使用；定義要求；研究外部/內部現有技術；映射當前系統行為；比較設計方案；做出單向決策；規劃階段；並維護即時決策日誌+未決問題積壓。觸發因素：規格、PRD、提案、技術規格、RFC、範圍、設計文件、端到端要求、階段計畫、權衡、開放性問題。 來源：inkeep/team-skills。