tech-blueprinting

⛔ GATE DISCIPLINE: host user-choice mechanism gates = hard stops. Never skip or auto-pick answer. Tool unavailable → numbered-text fallback → stop, wait for reply. No flag bypasses a gate; override flags pass only as user's recorded gate answer.

/tech-blueprinting

Release version: 2.0.0

Ground decisions and produce a reviewable brief. Default: ground → material decisions → brief → risk/contract review → handoff. Section collaboration is optional, not the default production line.

Routing

Ambiguous deliverable → a structured choice prompt ⛔ BLOCKING: README (Recommended) / General technical document. Fallback: numbered options in plain text; stop and wait.

Default workflow

• Ground ⛔ BLOCKING. Load shared doctrine and runtime adapter. Read supplied sources and existing document before editing; count lines before full reads. Establish audience, goal, impact, non-goals, destination and authority from existing context. Ask only for missing material context. Implementation docs: inspect scoped repo structure, commands, patterns, contracts, history and reuse before proposing architecture, using references/context-gathering-details.md.
• Material decisions ⛔ BLOCKING. Present grounded findings and consequential alternatives, not a fixed brainstorm quota. Record binding constraints versus provisional approach and reference examples. Invoke a structured choice prompt: Approve direction (Recommended) / Adjust direction / Add context. Fallback: numbered options in plain text; stop and wait. Existing explicit authorization covering this direction resolves the gate: cite its source and scope, do not re-ask. Missing material decisions or changed authority still require the gate; silence or inferred intent never answers it. Default to brief drafting, not a mandatory collaboration question. If user requests a choice of collaboration mode, a structured choice prompt: Draft brief (Recommended) / Collaborate by section. Fallback: numbered options in plain text; stop and wait. Explicit section collaboration loads workflows/section-drafting-loop.md.
• Draft brief. Cover problem, goal/non-goals, material decisions and rationale, contract boundaries, outcomes/proof, dependencies, owners and open risks. Implementation briefs use milestone contracts plus references/implementation-doc-requirements.md; no mandatory code-filled microsteps. Preserve approved exact content. Output: general Markdown written directly (or via a dedicated notes skill if installed), Word through a dedicated docx skill if installed; README route writes directly under its own workflow. Default general output a user-selected output path (e.g. ./outputs/). Scratch-only scope stays scratch; no durable save implied.
• Risk/contract review ⛔ BLOCKING. Dispatch independent agents/spec-reviewer.md with doc_path only; resolve blocking defects. Dispatch fresh agents/reader-tester.md with doc_content, test_questions, check_mode="full", no conversation. Questions test what to build, what remains local choice, proof, failure boundaries and escalation. No independent reviewer available → report incomplete review, do not simulate independence. Revise affected sections, then rerun affected checks. Grill stays optional via its route, never silently substituted for these reviews.
• Handoff ⛔ BLOCKING. Present brief, review evidence, unresolved decisions and exact destination. Existing explicit authorization covering delivery to that destination resolves this conversational handoff: cite source/scope and deliver without re-asking. Otherwise a structured choice prompt: Done (Recommended) / One more review. Fallback: numbered options in plain text; stop and wait. Present a visible reviewable artifact and concise decision digest before any unresolved gate; no mandatory separate-turn choreography in this default workflow. Missing material decisions, destination/save authority and publication-owner gates still block their dependent actions. Ready means material blockers resolved, not every local step prewritten. Offer /tech-implement <path> unless explicitly authorized implementation is already the next action; document approval alone is not permission to implement, commit or publish.