Writing Plans

This skill has been folded into ce-plan. Keep this wrapper only for compatibility and route execution-planning work to ce-plan using generic-plan mode.

Standards snapshot (March 2026)

• ce-plan is now the canonical owner for execution-planning behavior.
• Preserve this wrapper only so older references and invocations still land in the right place.
• Do not maintain a second independent planning doctrine here.

When to use

• The user asks for writing-plans explicitly.
• Older docs or neighboring skills still reference writing-plans.
• The request is really generic implementation sequencing and should be handled by ce-plan in generic-plan mode.

When not to use

• Do not author a separate planning workflow here.
• Do not keep this wrapper as a competing owner beside ce-plan.
• Do not use this wrapper when the caller can go straight to ce-plan.