planning-genius

Generate test-driven implementation plans with IMPLEMENTATION.md files from story descriptions.

1|Updated Mar 11, 2025
One-click install
npx skills add https://github.com/danielstewart77/hive_mind --skill planning-genius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-genius
Source: https://github.com/danielstewart77/hive_mind/tree/main/specs/skills/planning-genius
Command: npx skills add https://github.com/danielstewart77/hive_mind --skill planning-genius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, test-driven development (TDD) implementation plans from user stories, ensuring a structured and efficient coding process.

Core Features & Use Cases

  • Deep Codebase Exploration: Analyzes existing code patterns, conventions, and infrastructure to inform the plan.
  • TDD Plan Generation: Produces a step-by-step implementation guide with specific test cases (unit and integration).
  • Use Case: When a new feature story is defined, use this Skill to generate a precise IMPLEMENTATION.md file that outlines exactly what needs to be built, how to test it, and which existing patterns to follow, before any code is written.

Quick Start

Use the planning-genius skill to create a TDD implementation plan for the story located in the documents path C:\Users\dastewart\source\repos\LandAdmin\LandAdmin.Modules.Wells.Web\ClientApp\src\app\modules\lifecycle-update\documents\9576.

Frequently Asked Questions about planning-genius

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

FAQPage Schema
How do I generate a test-driven development plan from a user story?

To generate a test-driven development plan, provide a documents path containing a STORY-DESCRIPTION.md. The Skill explores codebase patterns and creates a detailed IMPLEMENTATION.md file with TDD steps.

What is the best way to map test cases to software requirements before coding?

Mapping test cases to requirements is handled by generating an implementation plan that defines specific unit and integration tests. This ensures observable behavior verification for each story requirement.

How does TDD plan generation analyze existing codebase conventions?

TDD plan generation analyzes existing codebase conventions by exploring infrastructure and patterns within the provided documents path. It uses these patterns to inform the step-by-step implementation guide.

Do I need a specific file format to start automated implementation planning?

Yes, automated implementation planning requires a documents path containing a STORY-DESCRIPTION.md file. The Skill reads this specific markdown file to generate the corresponding IMPLEMENTATION.md output.

Can I use this implementation planning approach for existing software architecture?

Yes, this implementation planning approach works for existing software architecture by deep-exploring current code patterns and conventions. It then maps new TDD steps to follow those established infrastructural patterns.

What limitations exist when generating TDD steps from story descriptions?

A key limitation is that TDD step generation operates strictly on a provided documents path containing the story description. It cannot infer requirements without this specific STORY-DESCRIPTION.md input format.