writing-plans

Generate implementation plans from specs with task decomposition and testing strategies.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill writing-plans-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/DuySeu/StockMind --skill writing-plans-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a project spec into a clear, executable plan before coding, reducing ambiguity and rework.

Core Features & Use Cases

It guides engineers through comprehensive plan creation, including file touchpoints, testing strategies, documentation needs, and commit-ready tasks. It emphasizes structured task decomposition (bite-sized steps), adherence to DRY and YAGNI principles, and alignment with best practices like TDD. It supports planning across workflows with dedicated sections for structure, review, and execution handoff.

Quick Start

Create a complete implementation plan for a given multi-step task specification.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert a project spec into an executable implementation plan?

To convert a project spec into an implementation plan, decompose multi-step tasks into bite-sized steps, define file structure touchpoints, and outline testing strategies. This generates commit-ready deliverables for execution handoff.

What is task decomposition for multi-subsystem projects?

Task decomposition for multi-subsystem projects is breaking down a comprehensive specification into bite-sized, executable steps. It ensures adherence to DRY and YAGNI principles while defining required plan artifacts and documentation needs.

How do I create a testing strategy before coding a new feature?

Create a testing strategy before coding by aligning with TDD best practices and defining required test artifacts within the implementation plan. This reduces ambiguity and rework by establishing clear validation steps for each task.

Does this planning approach work for complex multi-subsystem workflows?

Yes, this planning approach supports complex multi-subsystem workflows by defining dedicated sections for structure, review, and execution handoff. It guides comprehensive plan creation across interconnected project components.

What's the best way to structure commit-ready tasks from a design doc?

The best way to structure commit-ready tasks from a design doc is to enforce structured task decomposition with specific file touchpoints. This ensures each deliverable aligns with DRY, YAGNI, and TDD principles.