hedgehog-planning-intake

Convert project descriptions into BMAD-based technical build plans and TODO checklists.

26|4|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/skyf0xx/hedgehog --skill hedgehog-planning-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hedgehog-planning-intake
Source: https://github.com/skyf0xx/hedgehog/tree/main/src/skills/hedgehog-planning-intake
Command: npx skills add https://github.com/skyf0xx/hedgehog --skill hedgehog-planning-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of architectural drift and vague project requirements by forcing a disciplined, step-by-step planning process before any code is written.

Core Features & Use Cases

  • BMAD Integration: Executes a rigorous, multi-phase elicitation process (Brainstorming, PRD, UX, Research) to ensure project clarity.
  • Mechanical Enforcement: Automatically generates a project-specific TODO.md and design notes, ensuring the AI follows a verifiable build order.
  • Use Case: When starting a new full-stack TypeScript application, use this skill to convert your initial concept into a locked-in scope, domain module list, and technical build plan.

Quick Start

Run the hedgehog planning intake skill to initiate the BMAD elicitation process and generate your project roadmap.

Frequently Asked Questions about hedgehog-planning-intake

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

FAQPage Schema
How do I convert a project idea into a structured TDD plan?

You convert a project idea into a TDD plan by running the BMAD elicitation process to generate product briefs, PRDs, and immutable TODO checklists that enforce a mechanical build order for full-stack TypeScript applications.

What is the BMAD methodology for software architecture planning?

The BMAD methodology is a multi-phase elicitation process encompassing Brainstorming, PRD, UX, and Research to define scope boundaries and domain modules, ensuring project clarity before code is written.

How do I prevent architectural drift when starting a new TypeScript application?

Prevent architectural drift by generating project-specific design notes and a locked-in scope through a disciplined step-by-step planning process, ensuring the AI follows a verifiable build order.

Can I use this planning intake process for full-stack TypeScript scaffolding?

Yes, you can use this process for full-stack TypeScript scaffolding to define technical requirements, configure add-ons, and generate an immutable project roadmap before development begins.

How do I generate a mechanical build order for a full-stack application?

Generate a mechanical build order by eliciting UX specifications and PRDs to create immutable project documentation and TODO checklists, forcing a verifiable sequence of development tasks.

Do I need to define PRDs and UX specifications before scaffolding a TypeScript project?

Yes, defining PRDs and UX specifications is required because the elicitation process uses them to establish scope boundaries and domain modules, which are necessary to produce the build plan.