Decompose user goals into verifiable task lists saved to .ohc/plans/.
npx skills add https://github.com/iadr-dev/colab --skill writing-plans-iadr-dev
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/iadr-dev/colab/tree/main/skills/writing-plans Command: npx skills add https://github.com/iadr-dev/colab --skill writing-plans-iadr-dev
Writing plans that are vague, underspecified, or too big leads to wasted cycles, scope creep, and agent churn; this skill converts a goal into a precise, decomposed task list with clear success criteria and an explicit approval gate.
Run writing-plans by asking your agent to respond with the keyword "plan" for the work you want done, and confirm the proposed approach when prompted.
High-intent search queries and answers about installing and using this skill.
To break down a large project into an executable task list, this skill conducts a deep interview to clarify scope, then decomposes the work into independently verifiable tasks limited to two hours each with specific file scopes and agent assignments.
The best way to prevent scope creep during software development planning is to require explicit user confirmation on a selected approach from two to three proposed tradeoff options before committing to the full task decomposition and gating subsequent build actions.
To ensure traceability when building from external specification documents, this skill runs a document-intake process and embeds mandatory Sources and Traceability fields within the canonical plan template saved to the .ohc/plans/ directory.
Yes, you need explicit user approval before an agent starts building. The generated plan enforces a workflow gate that blocks all BUILD processes until the user reviews the saved plan and responds with the exact keyword "go".
You should not use this planning method for short tasks taking less than 30 minutes. The deep interview and approach selection process is specifically designed for building efforts that exceed 30 minutes and require strict task decomposition.
An agent clarifies requirements before generating a development plan by asking three to five focused questions targeting scope, constraints, risks, and existing patterns, ensuring the final plan precisely matches the user's initial goal.
rogsmeInitialize and plan a GSD project with essential documentation.
iadr-devNormalize PRDs, RFCs, diagrams, and wiki exports into a repo-grounded intake index.
ngocsangyemCoordinate a 7-phase feature workflow with approval gates and TDD.
mhdxbilalExecute lightweight ad-hoc tasks with atomic commits and concise summaries.
