Writing technical plans

Produce one reader-first technical plan that is both the architectural design and the execution contract. Give reviewers a concise path to the conclusion and give implementing agents enough decisions, principles, boundaries, and evidence to build a greenfield system without inventing architecture during implementation.

This is the primary skill for plans and RFCs; do not impose a generic report format on them. If the plan binds implementing agents, also load writing-agent-rules when available. If deciding where the plan belongs in a larger documentation system, load writing-technical-documentation when available; plans are lifecycle records, not permanent reference by default.

Select the mode and depth

Select one mode:

• Create: Draft a new canonical document.
• Revise: Patch an existing canonical document without losing unaffected detail.
• Lossless structural remap: Reorganize a source the user considers technically complete while preserving every information-bearing unit and cross-reference.
• Review: Diagnose a document without changing it.
• Clean-room handoff: Prepare an unbiased brief only when the user explicitly requests independent work.