plan

Generate structured Markdown implementation plans from PRDs and feature specs.

23|4|Updated Sep 5, 2013
One-click install
npx skills add https://github.com/drn/dots --skill plan-drn
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/drn/dots/tree/main/agents/skills/plan
Command: npx skills add https://github.com/drn/dots --skill plan-drn

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating detailed, actionable implementation plans from various source materials, ensuring clarity and structured execution for development tasks.

Core Features & Use Cases

  • Plan Generation: Creates comprehensive plans from PRDs, tech spikes, or feature specs.
  • Codebase Contextualization: Integrates current project state, structure, and history into the plan.
  • Structured Output: Generates plans in a standardized Markdown format with phases, tasks, and decision logs.
  • Use Case: When tasked with a new feature, use this Skill to generate a step-by-step implementation plan, including technical approach, testing strategy, and potential risks, directly within your project's context.

Quick Start

Use the plan skill to generate an implementation plan from the attached document 'feature-spec.md'.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an implementation plan from a feature specification?โ–ผ

To generate an implementation plan from a feature specification, provide the source document to the skill. It analyzes your codebase for context and outputs a structured Markdown plan with phases and tasks to your project directory.

Can I create a software development plan directly from a PRD?โ–ผ

Yes, you can create a software development plan directly from a PRD. The skill processes your product requirements document to identify integration points and generate a detailed, actionable task breakdown for your development workflow.

What is the best way to track implementation progress and decisions during software development?โ–ผ

The best way to track implementation progress is to use the generated plan file. The skill supports iterative progress tracking and decision logging directly within the Markdown plan, keeping your development context updated.

Does the plan generation tool analyze the existing codebase for technical context?โ–ผ

Yes, the plan generation tool analyzes the existing codebase for technical context. It evaluates your project structure and history to identify integration points, ensuring the resulting implementation plan aligns with your current code.

Where are the generated implementation plans stored in the project?โ–ผ

Generated implementation plans are stored as standardized Markdown files in the `context/plans/` directory. This structured output ensures your development tasks, phases, and decision logs remain organized within your project.

Can I use this skill to break down a tech spike into actionable development tasks?โ–ผ

Yes, you can use this skill to break down a tech spike into actionable development tasks. It processes the technical spike documentation to generate a step-by-step plan including the technical approach and testing strategy.