writing-plans

Generate task-by-task implementation plans with exact files, tests, and commands.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nadicodeai/argo-agent --skill writing-plans-nadicodeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/nadicodeai/argo-agent/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/nadicodeai/argo-agent --skill writing-plans-nadicodeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating clear, actionable plans for software features can be time-consuming and error-prone. This skill provides bite-sized, well-structured implementation plans that reduce ambiguity and accelerate delivery.

Core Features & Use Cases

  • Structured task breakdown: Each plan defines 2-5 minute tasks with precise file paths, code snippets, and tests.
  • Guidance for execution: Includes exact commands, verification steps, and commit messages to ensure traceability.
  • TDD-first workflow: Emphasizes test-driven development and iterative refinements with frequent commits.

Quick Start

Describe the feature you want to implement and I will generate a task-by-task implementation plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a software feature into bite-sized implementation tasks?

To break down a software feature into bite-sized implementation tasks, provide a feature description to generate a task-by-task plan with 2-5 minute steps, specifying exact files, tests, commands, and verification steps for reliable development.

How does test-driven development fit into an implementation plan workflow?

Test-driven development fits into an implementation plan workflow by enforcing TDD principles throughout the task breakdown, ensuring each bite-sized step includes specific tests, verification steps, and frequent commits for iterative refinements.

Can I generate a task plan that includes exact file paths and verification commands?

Yes, you can generate a task plan that includes exact file paths and verification commands. The structured task breakdown specifies precise file paths, code snippets, exact commands, and commit messages to ensure full traceability during execution.

What is the best way to create actionable plans for complex software features?

The best way to create actionable plans for complex software features is to generate a structured plan enforcing DRY and YAGNI principles. This reduces ambiguity by defining bite-sized tasks with exact tests and verification steps for each incremental phase.

Do I need subagent-driven development to execute these implementation plans?

No, you do not strictly need subagent-driven development, but the generated implementation plans are specifically structured and ready for execution via subagent-driven development to maximize fast and reliable delivery.

Why should I use a structured task breakdown instead of just writing a feature description?

You should use a structured task breakdown because creating clear, actionable plans manually is time-consuming and error-prone. A bite-sized plan reduces ambiguity by defining exact files and tests, accelerating software delivery.