writing-plans

Create implementation plans with file mappings, atomic tasks, and review checkpoints.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/idoberk/BoQAppFront --skill writing-plans-idoberk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/idoberk/BoQAppFront/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/idoberk/BoQAppFront --skill writing-plans-idoberk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a spec or requirements document into a clear, implementation-ready plan so engineers can start work without guessing the scope, file layout, or test strategy.

Core Features & Use Cases

  • Breaks large requests into small, testable tasks with exact file paths and step-by-step actions.
  • Maps out the files to create or modify before implementation begins, helping teams keep responsibilities separated and avoid tangled changes.
  • Includes testing, documentation, commit guidance, and review checkpoints for multi-step engineering work.

Quick Start

Ask the writing-plans skill to turn my spec into an implementation plan and save it in the requested plan file path.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a spec into an implementation plan for multi-step engineering tasks?

To turn a spec into an implementation plan, provide your requirements to generate atomic task steps with exact file paths, test instructions, and review checkpoints for execution-ready development.

What is the best way to decompose feature development into testable tasks?

Decomposing feature development involves breaking large requests into small, testable tasks with exact file mappings and step-by-step actions, ensuring responsibilities remain separated and changes avoid tangles.

How do I map out files to modify before starting a cross-file refactor?

Mapping out files for a cross-file refactor requires identifying exact file paths to create or modify before implementation begins, keeping team responsibilities separated and avoiding tangled code changes.

Does implementation planning work for TDD and code review workflows?

Implementation planning works for TDD and code review workflows by integrating testing instructions, documentation, commit guidance, and review checkpoints directly into the decomposed task steps.

When do I need task decomposition and spec analysis for a software engineering project?

You need task decomposition and spec analysis for feature development, refactors, and cross-file changes that require clear decomposition and exact file mapping before any code is touched.

Can I use worktree isolation for atomic task steps in an implementation plan?

Yes, worktree isolation can be applied to atomic task steps defined in the implementation plan, ensuring that testable tasks, exact file mappings, and review checkpoints execute cleanly without overlapping changes.