writing-plans

Writes structured implementation plans for multi-step work in dsmm deepwork mode.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/hugefiver/ocmm --skill writing-plans-hugefiver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/hugefiver/ocmm/tree/main/dsmm/skills/writing-plans
Command: npx skills add https://github.com/hugefiver/ocmm --skill writing-plans-hugefiver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step implementation after an approved design often loses track of goals, file responsibilities, and verification steps. This Skill enforces a durable written plan so complex work stays coordinated and testable. ## Core Features & Use Cases - Structured Plan Authoring: Captures goal, architecture, tech stack, source spec, and global constraints before coding begins. - Task Decomposition: Maps every file to a responsibility and breaks work into independently testable tasks with exact verification commands. - Use Case: After a dsmm design is approved, use this Skill to produce a step-by-step implementation plan with expected results for each task, then run plan review before writing any code. ## Quick Start Write an implementation plan for the approved design, breaking the work into independently testable tasks with verification commands.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan before coding?▼

State the goal, architecture, tech stack, source spec, and global constraints first. Then map every file to a responsibility, break work into independently testable tasks, and include exact verification commands with expected results.

When should I use the writing-plans skill?▼

Use it after an approved dsmm design when implementation needs durable multi-step coordination. It is intended for deepwork mode where work spans multiple files and tasks that must remain testable.

What should a good implementation plan include?▼

A good plan includes the goal, architecture, tech stack, source spec, global constraints, a file-to-responsibility mapping, independently testable tasks, and exact verification commands with expected results.

Does the plan need review before implementation starts?▼

Yes, run plan review before implementation when the active workflow requires it. This catches gaps in task decomposition and verification coverage before code is written.

When is writing a full plan not necessary?▼

Skip it for single-step changes or trivial edits that do not span multiple files or tasks. The Skill targets multi-step implementation where coordination and verification discipline matter.