dev-plan

Generates a TDD-based implementation plan from docs/goal.md and saves it to Obsidian as step files.

1|2|Updated Jul 5, 2024
One-click install
npx skills add https://github.com/uuta/dotfiles --skill dev-plan-uuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/uuta/dotfiles/tree/main/skills/dev-plan
Command: npx skills add https://github.com/uuta/dotfiles --skill dev-plan-uuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms project goals described in docs/goal.md into a structured TDD-based implementation plan, saves it to an Obsidian vault, and splits it into reusable step files.

Core Features & Use Cases

  • TDD-driven planning: Converts requirements into a test-first plan that guides development.
  • Obsidian vault integration: Persists the generated plan in a centralized knowledge base for easy reference.
  • Step file generation: Breaks the plan into discrete steps for incremental implementation.

Quick Start

Use the dev-plan skill to generate a plan from docs/goal.md and save it to Obsidian, then split the plan into step files.

Frequently Asked Questions about dev-plan

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

FAQPage Schema
How do I generate a TDD implementation plan from project documentation?

To generate a TDD implementation plan, you can use a tool that parses project documentation like docs/goal.md and converts the requirements into a structured, test-first plan. This process creates a stepwise development guide for incremental execution.

How do I split a software development plan into discrete execution steps?

You can split a software development plan into discrete execution steps by using a planning tool that generates individual step files. This breaks down a broader TDD implementation plan into granular, actionable tasks for incremental development.

Can I save my project workflow state and implementation plan directly to an Obsidian vault?

Yes, you can save your project workflow state and implementation plan directly to an Obsidian vault. The planning process integrates with Obsidian to persist your TDD plan in a centralized knowledge base for easy team reference.

What is a TDD-based implementation plan and when do I need it for software planning?

A TDD-based implementation plan is a structured project guide that prioritizes test-first development steps derived from your project goals. You need it when your development team requires a structured plan and stepwise execution for incremental implementation.

Does this TDD planning approach require a specific file format for project goals?

Yes, this TDD planning approach requires your project goals to be defined in a docs/goal.md file. The tool explicitly enforces reading this markdown documentation to generate the workflow state and subsequent implementation steps.