planning

To break down architecture goals into actionable tasks, this planning skill ingests session context and exploration findings to generate a structured task graph with dependencies and verification steps.

Documenting design decisions for traceability is achieved by recording design choices and architectural outlines produced during the complexity-aware planning interview phase of this skill.

Complexity-aware interviewing adapts task decomposition by scaling the depth of the planning protocol based on project complexity, ensuring massive features receive appropriately detailed task breakdowns.

Yes, you can generate a structured design outline by loading session.json and context.json along with exploration reports to inform the phase-by-phase planning protocol.

Yes, you need session.json and context.json files because the planning protocol requires reading these inputs to analyze session goals and context before producing tasks and design documents.

You should avoid using a structured planning protocol for trivial tasks where the overhead of generating design documents and dependency graphs outweighs the complexity of the implementation itself.