writing-plans

Translate task specifications into deterministic step-by-step implementation plans.

512|64|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/agnt-gg/agnt --skill writing-plans-agnt-gg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/agnt-gg/agnt/tree/main/backend/skills/writing-plans
Command: npx skills add https://github.com/agnt-gg/agnt --skill writing-plans-agnt-gg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams convert a spec or requirements into a detailed, actionable implementation plan, removing ambiguity and guiding execution.

Core Features & Use Cases

  • Structured planning: maps the spec to files to touch, tests to write, docs to update, and commit history to capture.
  • Task decomposition: breaks work into small, verifiable steps with clear inputs and outputs.
  • Review and handoff: includes a plan-review loop and handoff to execution subagents or tooling.

Quick Start

Create a comprehensive implementation plan for the given feature spec, outlining the required files, tests, docs, and commits.

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 software specification into an actionable implementation plan?

To turn a software specification into an implementation plan, you translate requirements into a deterministic, step-by-step workflow. This decomposes work into verifiable tasks with explicit checkpoints, file mappings, tests, and documentation.

What is task decomposition in software engineering planning?

Task decomposition in software engineering planning breaks complex specifications into small, verifiable execution steps. It maps out required files to touch, tests to write, and commits to capture, removing ambiguity for engineers.

How do I structure a software development plan for team handoff?

Structuring a software development plan for handoff requires a rigid format with a header, task sections, and explicit checkpoints. This produces a portable plan document and reproducible execution steps for subagents or tooling.

Does structured implementation planning work for end-to-end feature development?

Structured implementation planning works for end-to-end feature development by mapping the spec to required files, tests, docs, and commits. It ensures a deterministic, reproducible workflow with a plan-review loop before execution handoff.

What's the best way to ensure engineers follow implementation steps without ambiguity?

The best way to ensure engineers follow steps without ambiguity is applying a rigid plan structure with explicit checkpoints. This approach yields a portable plan document and reproducible execution steps, guiding execution deterministically.

Why should I use a plan-review loop before handing off development tasks?

You should use a plan-review loop before handing off tasks to verify that end-to-end software planning covers all file mappings, tests, and docs. This ensures the generated implementation plan is deterministic and reproducible.