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。