spec-init

/spec-init - Pre-PRD spec framing

/spec-init is a decomposition-safety gate, not architecture design. Its result is Pre-PRD Spec Status: ready_for_prd|blocked; the global SDD backbone and Foundation Dev Path remain intentionally pending for /spec-design after /prd-to-features.

<input_contract> Require .memory-bank/prd.md with all existing clarified-PRD markers:

type: prd
clarification_status: complete
constitution_checked: true

If any marker is missing or has another value, stop and route to /write-prd or /constitution according to the failed owner contract; do not frame the PRD as ready. Read relevant context from the Constitution, Product Brief, existing glossary.md, spec-backbone.md, pure spec-index.md, user scenarios, invariants, and canonical subject specs under architecture/, contracts/, domains/, states/, adrs/, testing/, guides/, and runbooks/.

Legacy .memory-bank/tech-specs/FT-*.md may be read as brownfield evidence only; it is not a target path for new specs. If the PRD is missing or too unclear to frame truthfully, stop and route to /write-prd. </input_contract>

<glossary_gate> Before any other framing, inspect .memory-bank/glossary.md. It is unfilled if missing, empty, or placeholder-only. In that case populate it from the Product Brief, clarified PRD, and other authoritative project sources; otherwise reconcile existing terms with current evidence.

Keep only evidenced definitions. If a conflicting meaning can affect decomposition, use the existing operator-decision blocker. Continue only when the glossary has no placeholders and its spec-index.md row matches it. </glossary_gate>

<hard_invariants>

• Do not create feature files, task records, implementation plans, feature-owned or FT-* design specs, full architecture decisions, source-of-truth hierarchy, API/OpenAPI details, DB migrations, deployment design, detailed state machines, or invented security posture.
• Do not set feature spec_design_status; /prd-to-features creates features and later design skills own that status.
• Keep .memory-bank/spec-index.md a pure registry. Readiness, open design questions, matrices, and handoffs belong in spec-backbone.md.
• Preserve any existing Global Backbone Planning Revision. /spec-init does not initialize or increment the post-PRD planning contract; a fresh bootstrap placeholder remains 0 until /spec-design succeeds.
• Keep boundary hints preliminary in spec-backbone.md#Decomposition Inputs. /spec-init does not create accepted module/change-unit nodes, dependency edges, or boundary contracts.
• Do not turn a later architecture question into a product assumption. Record it for /spec-design unless it blocks truthful L1-L3 decomposition now. </hard_invariants>

<operator_decisions> If an unresolved product/domain branch can change actors, core scenarios, non-goals, entity/business-rule ownership, lifecycles, boundary hints, constraints, risks, or feature/epic cuts, ask the operator before setting ready_for_prd.

Use an adaptive interview: ask one question or a small group of tightly related questions, explain decomposition impact, and optionally recommend an option. Do not run a fixed framing questionnaire. A recommendation is not a decision. Do not re-ask matters settled by authoritative PRD/Constitution/spec evidence.

In unattended flow, use only an already accepted authoritative decision. If none exists, record the question and affected decomposition inputs, set Pre-PRD Spec Status: blocked, and halt with HALT_BLOCKING_QUESTIONS.

After every accepted answer, apply the decision to its existing owning canonical artifact and to the corresponding spec-backbone.md decomposition input or blocker. Remove contradictory superseded wording and rerun the PRD, source-precedence, link, and decomposition-safety checks before setting ready_for_prd. Do not create a separate decision artifact or status. </operator_decisions>