plan

Generate structured implementation plans with tasks, tests, and commits.

20|3|Updated Aug 16, 2016
One-click install
npx skills add https://github.com/heyJordanParker/dotfiles --skill plan-heyjordanparker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/heyJordanParker/dotfiles/tree/main/claude/.claude/skills/plan
Command: npx skills add https://github.com/heyJordanParker/dotfiles --skill plan-heyjordanparker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable framework to turn ambiguous feature ideas into concrete, executable implementation plans, reducing ambiguity and handoffs between contributors.

Core Features & Use Cases

  • Structured Task Templates: generate a plan that lists touched files, the steps to implement them, tests to write, and the necessary commits.
  • Mode Support: supports writing plans and question-driven decision workflows to adapt to different planning needs.
  • Documentation Output: exports plans to docs/plans with a dated filename and references to design decisions for traceability.

Quick Start

Use the plan skill to create a new implementation plan for a feature. Save plans to docs/plans/YYYY-MM-DD-<feature-name>.md. Follow the Task Structure guidelines to detail touched files, steps, tests, and commits.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn feature ideas into actionable engineering tasks?

To turn feature ideas into actionable engineering tasks, you can generate a structured plan that lists touched files, implementation steps, tests to write, and necessary commits. This reduces ambiguity and handoffs between contributors.

What is the best way to document architectural decisions for software features?

Documenting architectural decisions for software features is handled through question-driven workflows that produce structured templates. These templates capture design decisions and export to docs/plans with dated filenames for traceability.

How do I create a consistent plan format for implementation tasks across my team?

Creating a consistent plan format for implementation tasks relies on a repeatable framework that enforces a standardized template. It specifies touched files, implementation steps, tests, and commits, saving outputs to a dedicated docs/plans directory.

Can I use a question-driven workflow to plan software architecture?

Yes, you can use a question-driven workflow to plan software architecture. This mode adapts to different planning needs by guiding you through structured decisions, which are then documented as architectural references within the exported plan.

Where are implementation plans stored for traceability?

Implementation plans are stored for traceability by exporting them to the docs/plans directory. They are saved using a dated filename format, YYYY-MM-DD-<feature-name>.md, ensuring chronological tracking and easy retrieval of architectural decisions.