phase-3-outline

Route change tasks into simple or complex tracks and write solution_outline.md.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill phase-3-outline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-3-outline
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/phase-3-outline
Command: npx skills add https://github.com/cuioss/plan-marshall --skill phase-3-outline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates the phase-3-outline workflow to produce structured solution outlines and deliverables by routing change tasks via a two-track approach: Simple for localized changes and Complex for codebase-wide discovery, while coordinating with domain, recipe, and domain skills as needed.

Core Features & Use Cases

  • Two-track routing: Simple for localized changes; Complex for codebase-wide discovery and analysis.
  • Deliverable generation: Maps discoveries to deliverables and writes solution_outline.md.
  • Domain and recipe integration: Resolves domain-specific outline skills or falls back to generic workflows; supports recipe-driven planning with deterministic outcomes.
  • Verification and logging: Performs Q-Gate validation for complex tracks and logs progress and artifacts for traceability.

Quick Start

Provide phase-2-refine outputs (track, clarified_request, domains, module_mapping, compatibility) to phase-3-outline to generate a solution_outline.md and deliverables.

Frequently Asked Questions about phase-3-outline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a solution outline from phase-2 refine outputs?

To generate a solution outline, provide phase-2-refine outputs such as track, clarified_request, domains, and module_mapping to route the change tasks and produce a solution_outline.md.

What is two-track routing for change task planning?

Two-track routing directs localized changes to a Simple track and codebase-wide discovery to a Complex track, ensuring the solution outline matches the scale of the required modifications.

When do I need Q-Gate validation for solution outlines?

Q-Gate validation is required for complex tracks during solution outline generation to verify codebase-wide discoveries before mapping them to deliverables and writing the final outline.

Can I use domain-specific outline skills instead of generic workflows?

Yes, the workflow resolves domain-specific outline skills for tailored deliverable generation and falls back to generic workflows when a specialized domain skill is unavailable.

How does recipe-driven planning work with solution outlines?

Recipe-driven planning integrates with the outline workflow to produce deterministic solution outlines and deliverables, bypassing ambiguous routing for well-defined change patterns.

What deliverables are produced after routing change tasks?

Routing change tasks produces a solution_outline.md file, mapped deliverables based on discovery, progress logs for traceability, and status metadata returned for downstream planning.