writing-plans

Generate implementation plans with file paths, tests, and commits.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tense-i/stock-market-simulator --skill writing-plans-tense-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/writing-plans
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill writing-plans-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to create comprehensive, step-by-step implementation plans before touching code, ensuring complete coverage of tasks, tests, documentation, and commits.

Core Features & Use Cases

  • Generate end-to-end task plans that specify touched files, required tests, docs, and commit messages.
  • Provide bite-sized tasks that align with DRY, YAGNI, and TDD principles.
  • Facilitate a dedicated worktree workflow and standardized plan storage at docs/plans.

Quick Start

Create a new plan document at docs/plans/YYYY-MM-DD-writing-plans.md using the template and follow the bite-sized steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan from a high-level spec?

To generate an implementation plan, provide a high-level spec to produce a comprehensive document specifying touched files, required tests, documentation, and commit messages for multi-step tasks.

What is the best way to plan multi-step software engineering tasks before coding?

Planning multi-step software engineering tasks requires breaking specs into bite-sized steps aligned with DRY, YAGNI, and TDD principles, ensuring complete coverage of file paths, tests, and commits.

How do I structure task management for a new development process?

Structure task management by creating a plan document at docs/plans/YYYY-MM-DD-writing-plans.md, following a standardized template to define bite-sized implementation steps and commit messages.

Does this project planning approach work with TDD and DRY principles?

Yes, this project planning approach explicitly aligns generated bite-sized tasks with DRY, YAGNI, and TDD principles to guide the development process and testing requirements.

Can I use this for product development and documentation planning?

You can use this for product development and documentation planning, as it applies to multi-step tasks across software engineering, generating explicit file paths and required tests.