skills.rest
tomasbasso
tomasbassoCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with tasks, tests, and commit hints from specifications.

Updated Apr 25, 2026
Search Tags:#planning#testing#versioning#implementation#spec#tasks
One-click install
npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill writing-plans-tomasbasso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tomasbasso/SistemaStockV2/tree/main/.agents/skills/creacion-de-planes-de-desarrollo
Command: npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill writing-plans-tomasbasso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert high-level specifications into structured, executable implementation plans so teams can confidently proceed with design, development, and testing.

Core Features & Use Cases

  • Generates step-by-step tasks, tests, and commit hints from a specification.
  • Enforces a standardized plan document header and file naming convention for version control.
  • Enables saving plans to a dedicated docs/plans path for reuse and auditing.

Quick Start

Generate a comprehensive implementation plan and save it to docs/plans/YYYY-MM-DD-writing-plans.md.

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 high-level specification into an actionable implementation plan?▼

To turn a high-level specification into an implementation plan, provide the spec to generate step-by-step tasks, tests, and commit hints. The output is structured with a standardized header and saved to docs/plans for version control and auditing.

What is the best way to structure implementation tasks and tests for multi-step software projects?▼

The best way to structure implementation tasks and tests is using a standardized plan layout. This layout enforces a document header, detailed task steps, associated tests, and versioned commit hints to guide engineers through multi-step software projects.

How does saving implementation plans to a designated docs path help with version control?▼

Saving implementation plans to a designated docs/plans path with a standardized file naming convention enables version control, reuse, and auditing. It ensures teams can confidently track and reference structured executable plans across multi-step projects.

Can I use this approach to plan process automations and design tasks, not just software engineering?▼

Yes, you can use this planning approach for process automations and design tasks. It generates comprehensive implementation plans with tasks, tests, and commit hints applicable to any multi-step project requiring structured execution.

Do I need a specific format for my specification before generating an implementation plan?▼

You need a high-level specification to generate an implementation plan. The system requires a frontmatter section containing the name and description to successfully create the standardized plan layout with tasks, tests, and documentation.

Related Skills

Explore More Software Engineering Skills→
gotalabgotalab
406

notion-spec-to-implementation

Transforms Notion spec documents into actionable implementation plans and tasks with progress tracking.

Community
Basic
sixscripts-aisixscripts-ai

writing-plans

Convert high-level specs into detailed executable software plans.

Community
Intermediate
HouseGarofaloHouseGarofalo
3

harness-coder

Coordinate autonomous multi-session coding tasks with testing and version control.

Official
Advanced
aroidoaroido

agent-task-manager

Manage GitHub Projects tasks by creating issues, updating statuses, and organizing boards.

Official
Intermediate