@josstei/maestro 1.6.4-nightly.20260430

package/src/skills/shared/delegation/protocols/agent-base-protocol.md

@@ -0,0 +1,145 @@
+# Agent Base Protocol
+
+This protocol is injected into every delegation prompt by the delegation skill. It defines mandatory pre-work procedures and output formatting that all agents must follow regardless of their specialization.
+
+---
+
+## CRITICAL: File Writing Rule
+
+ALWAYS use `write_file` for creating files and `replace` for modifying files.
+
+NEVER use `run_shell_command` to write file content. This includes:
+- `cat`, `cat >>`, `cat << EOF`
+- `echo`, `printf`
+- Heredocs (`<< EOF`, `<< 'EOF'`)
+- Any shell redirection for content (`>`, `>>`)
+
+Shell interpretation corrupts YAML frontmatter, Markdown syntax, backticks, brackets, and special characters. This rule has NO exceptions.
+
+If `write_file` is not in your authorized tool list, you cannot create files. Report the limitation in your Task Report rather than using shell workarounds.
+
+---
+
+## CRITICAL: No Interactive Commands
+
+You run autonomously without user input. NEVER use commands that require interactive stdin:
+- `npx create-*` (scaffolding wizards)
+- `npm init` (without `-y`)
+- `git rebase -i` (interactive rebase)
+- Any CLI tool that prompts for user choices
+
+If a task requires project scaffolding, create the files directly via `write_file` instead of using interactive generators. If you need a `package.json`, write it. If you need a config file, write it. Do not rely on CLI wizards.
+
+---
+
+## Pre-Flight Protocol
+
+Execute these three steps in order before beginning any task work. Do not skip steps. Do not begin producing deliverables until all three steps are complete.
+
+### Step 1 — Anchor to Project Reality
+
+Before producing any output:
+
+- Read every file listed in the delegation prompt in full — do not scan or skim
+- Identify the language, framework, and runtime from project configuration files (`package.json`, `go.mod`, `Cargo.toml`, `pyproject.toml`, `pom.xml`, `build.gradle`, `Gemfile`, `*.csproj`)
+- Detect existing patterns in the codebase: naming conventions, directory structure, error handling style, dependency injection approach, test framework and conventions
+- Record these observations as internal working context — every subsequent decision must be consistent with what you found
+
+### Step 2 — Scope Verification
+
+Before starting work, confirm:
+
+- Files listed for modification in the delegation prompt exist
+- Files listed for creation have existing parent directories
+- The task objective is achievable within your tool permissions — if not, report the limitation immediately rather than attempting workarounds
+- The task does not duplicate or conflict with work described as completed in the progress context
+- No files outside the delegation prompt's explicit file list will be touched
+
+If any verification fails, report the issue in your Task Report and stop. Do not improvise around scope or permission constraints.
+
+### Step 3 — Convention Extraction
+
+Identify and match the project's established conventions:
+
+- **Naming**: How are files, classes, functions, and variables named? Match exactly. Do not introduce alternative conventions.
+- **Structure**: How is code organized across directories? What types of code go where? Follow the existing grain.
+- **Patterns**: What architectural patterns are already in use (repositories, services, controllers, middleware, etc.)? Extend them — do not introduce competing patterns for the same concern.
+- **Error handling**: How does this project handle errors (custom error classes, result types, try/catch conventions)? Use the same approach.
+- **Testing**: What test framework, naming conventions, and organization patterns are used? Follow them exactly.
+
+If any convention is ambiguous or no precedent exists, default to the most common pattern observed across the codebase. If fewer than 3 examples exist, note the ambiguity in your Handoff Report.
+
+---
+
+## Output Handoff Contract
+
+Every agent must conclude with a **Handoff Report** containing two parts. This replaces the basic Task Report with a format designed for downstream consumption.
+
+### Part 1 — Task Report
+
+```
+## Task Report
+- **Status**: success | partial | failure
+- **Objective Achieved**: [One sentence restating the task objective and whether it was fully met]
+- **Files Created**: [Absolute paths with one-line purpose each, or "none"]
+- **Files Modified**: [Absolute paths with one-line summary of what changed and why, or "none"]
+- **Files Deleted**: [Absolute paths with rationale, or "none"]
+- **Decisions Made**: [Choices made that were not explicitly specified in the delegation prompt, with rationale for each, or "none"]
+- **Validation**: pass | fail | skipped
+- **Validation Output**: [Command output or "N/A"]
+- **Errors**: [List with type, description, and resolution status, or "none"]
+- **Scope Deviations**: [Anything asked but not completed, or additional necessary work discovered but not performed, or "none"]
+```
+
+### Part 2 — Downstream Context
+
+Populate this section when your output feeds into subsequent phases. Read-only agents populate this with findings structured as actionable items.
+
+```
+## Downstream Context
+- **Key Interfaces Introduced**: [Type signatures and file locations, or "none"]
+- **Patterns Established**: [New patterns that downstream agents must follow for consistency, or "none"]
+- **Integration Points**: [Where and how downstream work should connect to this output — specific files, functions, endpoints, or "none"]
+- **Assumptions**: [Anything assumed that downstream agents should verify, or "none"]
+- **Warnings**: [Gotchas, edge cases, or fragile areas downstream agents should be aware of, or "none"]
+```
+
+### Rules
+
+- Part 2 is mandatory when the phase has downstream dependencies (phases that list this phase in their `blocked_by`)
+- Part 2 may be omitted only when the phase has no downstream dependencies AND is the final phase
+- The orchestrator extracts Downstream Context from completed phases and includes relevant sections in subsequent delegation prompts, creating an information chain
+- Be specific in Downstream Context — reference exact file paths, function names, and type signatures rather than general descriptions
+
+### Canonical Shape for `transition_phase`
+
+When the orchestrator translates your Markdown Downstream Context into the `downstream_context` argument of `transition_phase`, the server enforces a fixed shape:
+
+- The object keys are exactly `key_interfaces_introduced`, `patterns_established`, `integration_points`, `assumptions`, `warnings` (snake_case). Other keys are dropped.
+- Each value is either a string or an array of strings. The server normalizes strings to single-element arrays.
+- The tokens `"none"`, `"n/a"`, `"not applicable"`, and empty strings are treated as absent.
+- A phase that produced files but whose normalized context has no non-empty field is rejected with `HANDOFF_INCOMPLETE` — the orchestrator must re-request a populated handoff.
+
+Prefer arrays when you have multiple discrete items so each item is preserved verbatim in session state.
+
+### Hook Enforcement
+
+The hooks system validates this contract at runtime. After every agent turn, the post-delegation hook checks for both `## Task Report` and `## Downstream Context` headings in the response:
+
+- **Missing either heading on first attempt**: The hook blocks the response and returns a retry request specifying which section is absent. The agent must re-produce the complete handoff report.
+- **Missing either heading on retry**: The hook allows the response through to prevent infinite loops, but logs a warning. The orchestrator receives the malformed output and must handle the missing context.
+
+Always include both headings, even when Part 2 fields are all "none". Omitting the heading entirely triggers the retry mechanism and adds unnecessary latency.
+
+## Blockers
+
+If you cannot proceed because a user decision is required, emit a `## Blockers` section in your handoff, placed between `## Task Report` and `## Downstream Context`:
+
+    ## Blockers
+    - BLOCKER: [your question]
+      Context: [why this arose; what you tried]
+      Required to proceed: [the specific answer you need]
+
+Do NOT call a user-prompt tool yourself. The orchestrator will collect blockers, ask the user, and re-delegate the phase with the answer supplied in your next delegation Context.
+
+A handoff that lists blockers does NOT count as phase completion. Your phase stays `in_progress` until you return again without blockers.

package/src/skills/shared/delegation/protocols/filesystem-safety-protocol.md

@@ -0,0 +1,31 @@
+# Filesystem Safety Protocol
+
+This protocol is injected into every delegation prompt alongside the Agent Base Protocol. It defines mandatory filesystem safety rules that all agents must follow to prevent errors from missing directories.
+
+---
+
+## Rule 1 — Ensure Before Write
+
+Before any file creation, write, or move operation, verify the target's parent directory exists. If it doesn't, create it using `mkdir -p`. This applies to every file operation that produces output at a path — writes, moves, copies, renames.
+
+**Protocol Override:** This rule modifies the base protocol's Scope Verification Step 2, specifically the check "Files listed for creation have existing parent directories." When parent directories are missing, create the missing directory using `mkdir -p` and continue with the file operation. Do NOT stop and report the issue as a verification failure. All other Step 2 verifications (file existence, tool permissions, scope boundaries) remain in effect.
+
+## Rule 2 — Silent Success, Clear Failure
+
+Directory creation is a precondition, not a noteworthy event. Do not report successful directory creation. Only report failures (permission denied, disk full) immediately as a blocker in the Task Report.
+
+## Rule 3 — Never Assume Directory State
+
+Treat every directory reference as potentially non-existent, even if a prior phase "should have" created it. Phases run independently (especially in native parallel batches). Each agent ensures its own write targets exist.
+
+## Rule 4 — Path Construction
+
+Always construct full paths before writing. Never write to a path assembled from unverified components. For target project operations, verify the project root exists and is writable before creating subdirectories.
+
+## Rule 5 — Scope
+
+This protocol applies to Maestro state directories, target project directories, and archive operations.
+
+## Rule 6 — Write Tool Only
+
+All file content must be written using `write_file` or `replace` tools. Never use `run_shell_command` with `cat`, `echo`, `printf`, heredocs, or shell redirection (`>`, `>>`) to create or modify file content. Shell interpretation corrupts structured content (YAML, Markdown, JSON, code with special characters). This reinforces the Agent Base Protocol's File Writing Rule.

package/src/skills/shared/design-dialogue/SKILL.md

@@ -0,0 +1,284 @@
+---
+name: design-dialogue
+description: Guides structured design conversations for complex engineering tasks
+---
+
+# Design Dialogue Skill
+
+**Standard workflow only.** If `task_complexity` is `simple` and workflow mode is Express, do not activate this skill. Simple tasks use the Express workflow, which does not activate design-dialogue. Return to the Express Workflow section.
+
+Activate this skill when beginning Phase 1 of Maestro orchestration. Use the plan mode tool from `get_runtime_context` (loaded at session start, step 0). If your runtime provides a Plan Mode surface, enter it now by calling `enter_plan_mode`. If Plan Mode is unavailable or the transition fails, continue without it and use the user-prompt tool from runtime context with `type: 'yesno'` for design approvals and `type: 'choice'` for approach selection. This skill provides the structured methodology for conducting design conversations that converge on approved architectural designs.
+
+**User confirmation sequence**: Phase 1 entry may trigger a Plan Mode confirmation when `enter_plan_mode` is available. That confirmation is expected; do not treat it as redundant or skip it. If your runtime does not provide Plan Mode, move directly into the depth selector and approval prompts.
+
+## Design Depth Gate
+
+Before asking any design questions, present the user with a depth selector to control the level of reasoning rigour applied throughout the design phase. Use `ask_user` with `type: 'choice'` to offer three modes. Lead with Standard as the recommended default.
+
+**Modes:**
+
+- **Quick** — Current reasoning behavior. One question per topic, pros/cons on approaches, standard design sections. No enrichment steps, no decision matrix, no reasoning annotations. Choose this when you already have clarity and want to move fast. (The depth selector prompt itself is the only new conversational step — once Quick is selected, all subsequent behavior matches pre-change behavior exactly.)
+- **Standard** (Recommended) — Adds assumption surfacing after each answer and a decision matrix during approach evaluation. Design sections gain rationale annotations tying decisions to project context. The default for most work.
+- **Deep** — Full treatment. Follow-up probing into implications, assumption surfacing with confirmation, trade-off narration on each choice, decision matrix with scoring, rationale annotations, per-decision alternatives, and full requirement traceability. Choose this for high-stakes or ambiguous tasks.
+
+**Depth propagation**: Remember the user's chosen depth mode and apply it consistently to all subsequent steps in this skill. The depth mode is not re-prompted — it is set once and carried forward. If the user's answer to the depth prompt is ambiguous, default to Standard.
+
+**Depth vs. complexity**: Depth and complexity guidance (simple/medium/complex) are orthogonal. Complexity controls which sections appear and word count per section. Depth controls reasoning richness within each section. They compose independently — a user may select Deep depth on a Simple complexity task or Quick depth on a Complex task. Both are valid choices.
+
+**Frontmatter**: Record the chosen depth in the design document frontmatter as `design_depth: quick | standard | deep`. Also record `task_complexity: simple | medium | complex` in the design document frontmatter after `design_depth`.
+
+**First-Turn Contract**: On the first turn, Maestro presents the complexity classification result (classified per the complexity classification section in the orchestrator) and the depth selector with a complexity-informed recommendation. For `simple` tasks, auto-select Quick and inform the user: "This looks straightforward — using Quick depth. Say 'deeper' if you want more analysis." For `medium` tasks, recommend Standard. For `complex` tasks, recommend Standard or Deep. The first actual design question moves to the second turn.
+
+## Repository Grounding Protocol
+
+Before you start narrowing the architecture for work that touches an existing codebase, decide whether the task is already grounded.
+
+Use the built-in `codebase_investigator` when any of the following are true:
+- The request targets an existing project or subsystem
+- The current architecture, impacted modules, or integration seams are unclear
+- You need concrete validation commands, conventions, or ownership boundaries before presenting approaches
+
+Ask the investigator for:
+- The current architecture slice relevant to the task
+- The most likely impacted modules and files
+- Existing naming, layering, and testing conventions to preserve
+- Integration points and dependency edges the design must respect
+- Validation commands already used by the repo
+- Parallelization or file-conflict risks that should shape the later implementation plan
+
+Skip `codebase_investigator` for greenfield tasks, documentation-only work, or scopes that are already well understood from direct file reads in the current turn.
+
+Use the investigator's output to:
+- Tailor follow-up questions to the actual codebase
+- Avoid proposing approaches that conflict with existing boundaries
+- Cite concrete modules/files when explaining trade-offs
+
+## Question Framework
+
+### Principles
+- Ask one question at a time — never batch multiple questions
+- Prefer multiple choice format with 2-4 options over open-ended questions
+- For every choice presented, include brief pros and cons so the user can make an informed decision — never present bare options without trade-off context
+- Lead with your recommended option and explain the rationale
+- Wait for user response before proceeding to next question
+- Adapt follow-up questions based on previous answers
+
+### Required Coverage Areas
+
+Ask questions in this order to progressively narrow the design space:
+
+1. **Problem Scope & Boundaries**
+   - What specific problem are we solving?
+   - What is explicitly out of scope?
+   - What are the expected inputs and outputs?
+
+2. **Technical Constraints & Limitations**
+   - Existing technology stack and infrastructure
+   - Compatibility requirements with existing systems
+   - Performance budgets (latency, throughput, resource limits)
+   - Team expertise and familiarity
+
+3. **Technology Preferences**
+   - Language and framework preferences
+   - Database and storage requirements
+   - Third-party service dependencies
+   - Build and deployment toolchain
+
+4. **Quality Requirements**
+   - Performance targets (response time, concurrent users)
+   - Security requirements (authentication, authorization, data protection)
+   - Scalability expectations (growth projections, peak loads)
+   - Reliability requirements (uptime, disaster recovery)
+
+5. **Deployment Context**
+   - Target environment (cloud provider, on-premise, hybrid)
+   - CI/CD pipeline requirements
+   - Monitoring and observability needs
+   - Operational constraints (team size, on-call, maintenance windows)
+
+### Coverage Scaling by Complexity
+
+Scale question coverage based on `task_complexity`:
+- **simple**: Ask questions from Area 1 (Problem Scope & Boundaries) only. Skip Areas 2-5.
+- **medium**: Ask questions from Areas 1-3 (Scope, Constraints, Tech Preferences). Skip Areas 4-5.
+- **complex**: Ask questions from all 5 areas (current behavior).
+
+### Question Format
+
+Prompt the user for a choice using the user-prompt tool from runtime context. Use `type: 'choice'` for structured selections with 2-4 options. Each option should have a short label (1-5 words) and a description explaining when it makes sense and its trade-offs. Include your recommendation rationale in the question text so the user has context before choosing.
+### Enrichment Protocol
+
+After the user answers each question, apply depth-gated enrichment steps before advancing to the next topic:
+
+| Step | Quick | Standard | Deep |
+|------|-------|----------|------|
+| Accept answer and move on | Yes | Yes | Yes |
+| Surface assumptions made from the answer | No | Yes | Yes |
+| Ask user to confirm/correct assumptions | No | Yes | Yes |
+| Probe implications with a follow-up question | No | No | Yes |
+| Narrate trade-offs of the choice before moving on | No | No | Yes |
+
+**Quick mode**: No enrichment steps. Accept the answer and proceed to the next question. Current behavior preserved.
+
+**Standard mode**: After each user answer, state the assumptions you are making based on their response in 1-2 sentences, then ask the user to confirm or correct before proceeding. Example flow: question → answer → "Based on your answer, I'm assuming X and Y — correct?" → confirmation → next question.
+
+**Deep mode**: After each user answer: (a) state and confirm assumptions as in Standard mode, (b) narrate the trade-offs of the choice in 1-2 sentences ("That choice means we gain A but give up B"), (c) if the answer has non-obvious implications (e.g., a technology choice that constrains future scaling options or creates a vendor lock-in dependency), ask one follow-up probing question before moving to the next topic. Cap at one follow-up per question.
+
+**Adaptive elision**: If the user's answer is concrete, specific, and requires no inference (e.g., "What language?" → "TypeScript, same as the rest of the repo"), the assumption surfacing and trade-off narration steps may be skipped even in Deep mode. Only apply enrichment when there are genuine assumptions to surface or trade-offs to narrate. Do not elide when the answer implies unstated architectural trade-offs even if the answer itself is short (e.g., "REST" implies choices about state management, versioning, and contract evolution that are worth surfacing).
+
+## Approach Presentation
+
+### When to Present Approaches
+Present 2-3 architectural approaches after gathering sufficient requirements (typically after covering scope, constraints, and technology preferences).
+
+If `codebase_investigator` was used, present approaches only after incorporating its findings into the trade-off analysis. Do not treat the existing codebase structure as optional context.
+
+### Approach Format
+
+For each approach, provide:
+
+```
+### Approach [N]: [Descriptive Name]
+
+**Summary**: [2-3 sentence overview]
+
+**Architecture**:
+[Component diagram or description showing key components and their relationships]
+
+**Pros**:
+- [Concrete advantage with context]
+- [Another advantage]
+
+**Cons**:
+- [Concrete disadvantage with context]
+- [Another disadvantage]
+
+**Best When**: [Specific conditions where this approach excels]
+
+**Risk Level**: Low | Medium | High
+```
+
+### Presentation Rules
+- Always lead with your recommended approach
+- Explain why the recommended approach best fits the gathered requirements
+- Highlight the key differentiator between approaches
+- After presenting all approaches, explicitly ask the user to choose
+- Accept user's choice without pushback, even if it differs from your recommendation
+
+### Recommendation Philosophy
+- **Always identify the ideal long-term solution** — the approach that is architecturally sound, maintainable, and future-proof. Present it clearly so the user understands what "right" looks like.
+- **When the long-term solution requires large-scale changes** that are disproportionate to the task at hand, also present a pragmatic alternative that accomplishes the goal without major disruption. Be explicit about the trade-off: "The ideal solution is X (because...), but a pragmatic path is Y (because the scope of X is disproportionate to the current need)."
+- **Never default to the quick fix without surfacing the long-term option.** The user should always know what they're trading away. But equally, never recommend a large-scale refactor when the task can be accomplished safely with a targeted change.
+- **Label each approach honestly**: which is the long-term investment, which is the pragmatic path, and which (if any) is a stopgap that will create debt.
+
+### Decision Matrix
+
+In Standard and Deep modes, after presenting the 2-3 approaches with narrative pros/cons, also present a decision matrix that scores each approach against the gathered requirements. In Quick mode, skip the matrix.
+
+**Criteria derivation**: Derive 3-6 scoring criteria from the requirements and constraints gathered during the question phase. Use the user's stated priorities to assign weights (sum to 100%). If the user has not explicitly stated priorities, infer relative weights from the emphasis given during the question phase; equal weighting is acceptable as a last resort. If fewer than 3 meaningful criteria emerge, skip the matrix and use narrative-only recommendation.
+
+**Scoring scale**: Score each approach on each criterion using a 1-5 scale: 1=poor fit, 3=adequate, 5=strong fit. Include a brief justification (1 sentence) in each cell.
+
+**Matrix format**:
+
+| Criterion | Weight | Approach A | Approach B | Approach C (if applicable) |
+|-----------|--------|------------|------------|------------|
+| [Criterion from requirements] | [%] | [1-5]: [justification] | [1-5]: [justification] | [1-5]: [justification] |
+| **Weighted Total** | | [score] | [score] | [score] |
+
+**Tie-breaking**: If approaches score within 1 point of each other in weighted totals, present the near-tie explicitly and use narrative judgment to break the tie, citing the single most decisive factor. Do not present a matrix-driven recommendation as definitive when the scores don't clearly differentiate.
+
+**Non-differentiating criteria**: Criteria that score identically across all approaches may be noted but should be excluded from the matrix to keep it focused on differentiating factors. If removing non-differentiating criteria leaves fewer than 2 rows, skip the matrix and use narrative-only recommendation.
+
+## Design Convergence Protocol
+
+### Section-by-Section Presentation
+
+Present the design document in sections, validating each before proceeding. Scale the number of sections to the task's complexity, but always present at least the **minimum set**.
+
+**Minimum sections (always required, regardless of task complexity):**
+1. Problem Statement
+2. Approach (Selected Approach, Alternatives Considered)
+3. Risk Assessment
+
+**Full presentation order** (use for medium-to-complex tasks; matches `templates/design-document.md` structure):
+1. Problem Statement
+2. Requirements (Functional, Non-Functional, Constraints)
+3. Approach (Selected Approach, Alternatives Considered, Decision Matrix)
+4. Architecture (Component Diagram, Data Flow, Key Interfaces)
+5. Agent Team
+6. Risk Assessment
+7. Success Criteria
+
+**Complexity guidance:**
+- **Simple** (static sites, single-file scripts, config changes): present the 3 minimum sections. Keep each to 100-150 words.
+- **Medium** (multi-component features, API endpoints, integrations): present sections 1-3 and 6, plus up to 1 other section that surfaces meaningful trade-offs (cap at 5 total). 150-250 words each.
+- **Complex** (new subsystems, cross-cutting refactors, multi-service architectures): present all 7 sections at 200-300 words each.
+
+Never skip Problem Statement, Approach, or Risk Assessment. If you believe other sections add no value for the task, omit them — but state which sections you are skipping and why before presenting the first section.
+
+### Validation Format
+
+After each section, prompt the user for approval using the user-prompt tool from runtime context with `type: 'yesno'`. Do not rely on a separate assistant message for the section content. The prompt body itself must include the section title and the full section summary (200-300 words) so the user can review the material directly in the approval prompt. End with: "Does this section accurately capture our discussion? Any changes needed before I proceed to [next section name]?"
+
+### Revision Protocol
+- If user requests changes, revise the section and re-present
+- Re-present revised content inside the next approval prompt as well; never ask for approval on a section summary the user cannot see in the prompt
+- Track which sections are approved vs pending
+- Do not proceed to the next section until current section is approved
+- If a later section reveals issues with an earlier section, flag the conflict and propose resolution
+
+### Section Reasoning Guide
+
+Apply depth-gated reasoning enrichment to design section content during the convergence phase:
+
+| Element | Quick | Standard | Deep |
+|---------|-------|----------|------|
+| Pros/cons on approaches | Yes | Yes | Yes |
+| Recommendation narrative | Yes | Yes | Yes |
+| Decision matrix scoring approaches | No | Yes | Yes |
+| Rationale annotations on section decisions | No | Yes | Yes |
+| Per-decision alternatives considered | No | No | Yes |
+| Requirement traceability (`Traces To`) | No | No | Yes |
+
+**Quick mode**: No reasoning annotations. Present sections as-is — current behavior preserved.
+
+**Rationale annotations (Standard + Deep)**: For each key design decision within a section, include an inline explanation of why it was chosen, tied to specific project context from the question phase. A key decision is one that, if changed, would require reworking other parts of the design — routine or cosmetic choices (naming, formatting) are not key. Format: `[decision] — *[rationale referencing specific requirements, constraints, or user-stated preferences]*`
+
+**Per-decision alternatives (Deep only)**: For key sub-decisions (choices within a section that affect the design's shape), briefly note what was considered and rejected. Format: `[decision] *(considered: [alternative A] — rejected because [reason]; [alternative B] — rejected because [reason])*`
+
+**Requirement traceability (Deep only)**: Tag each key decision with `Traces To: REQ-N` referencing the numbered requirement it satisfies from the design document's Requirements section. Every requirement (functional and non-functional) should be traceable to at least one design decision. If the Requirements section was omitted due to complexity guidance (simple tasks), skip requirement traceability markers — rationale annotations and per-decision alternatives still apply.
+
+**Uniform application**: Apply the chosen depth mode's reasoning rules uniformly to every section in the convergence phase. Do not selectively skip reasoning on some sections unless the adaptive elision rule applies (the decision is self-evident and requires no justification).
+
+## Design Document Generation
+
+### Output Location
+
+The write path depends on whether your runtime provides a Plan Mode surface (check `get_runtime_context`, loaded at session start, step 0):
+
+- **Plan Mode active**: Some runtimes restrict writes to a temporary staging directory during Plan Mode. Write the design document there first, then exit Plan Mode and complete the design approval handoff. When the runtime's Plan Mode path is not visible to the MCP server, use the `record_design_approval` content variant so the server materializes the canonical copy under `<state_dir>/plans/`.
+- **Plan Mode not active or not available**: Write directly to the permanent location. If your runtime does not provide Plan Mode, track design progress using the plan-update mechanism from runtime context and use the user-prompt tool from runtime context for section approvals and final signoff.
+
+Permanent location: `<state_dir>/plans/YYYY-MM-DD-<topic-slug>-design.md` (where `<state_dir>` resolves from `MAESTRO_STATE_DIR`, default `docs/maestro`).
+
+Where:
+- `YYYY-MM-DD` is the current date
+- `<topic-slug>` is a lowercase, hyphenated summary of the task (e.g., `user-auth-system`, `data-pipeline-refactor`)
+
+### Document Structure
+Use the `design-document` template loaded via `get_skill_content`. Include the `design_depth` field in the frontmatter, set to the depth mode chosen during the Design Depth Gate.
+
+### Completion Criteria
+The design document is complete when:
+- All sections have been presented and approved by the user
+- The agent team composition matches the task requirements
+- Phase dependencies are clearly mapped
+- Success criteria are measurable and specific
+- The user has given explicit final approval of the complete document
+
+### Post-Generation
+After writing the design document:
+1. Confirm the file path to the user
+2. Summarize key decisions made during the dialogue
+3. Ask if the user is ready to proceed to implementation planning (Phase 2)