Generate requirements, architecture, and epics documents via interactive Q&A.
npx skills add https://github.com/stharrold/german --skill bmad-planner
Please help me install this Agent Skill. Skill: bmad-planner Source: https://github.com/stharrold/german/tree/main/.claude/skills/bmad-planner Command: npx skills add https://github.com/stharrold/german --skill bmad-planner
This Skill addresses the challenge of creating comprehensive, consistent, and well-structured planning documents (requirements, architecture, epics) before development begins. It eliminates manual document creation, ensures alignment, and saves significant time and AI tokens by providing a structured Q&A process.
requirements.md, architecture.md, and epics.md from rich templates, pre-populating them with your interactive responses.contrib branch.python .claude/skills/bmad-planner/scripts/create_planning.py
my-feature stharrold
High-intent search queries and answers about installing and using this skill.
Planning document generation automates creation of requirements, architecture, and epics files through an interactive three-persona Q&A process. The Skill guides you through Analyst, Architect, and PM perspectives, then commits structured artifacts to your contrib branch, eliminating manual document creation and saving up to 92% in AI token usage.
Epic breakdown happens through the PM persona's interactive questions in the planning workflow. The Skill generates prioritized epics directly into an `epics.md` file based on your responses, ensuring work is decomposed consistently before implementation begins.
Yes. The three-persona approach covers requirements gathering (Analyst), architecture design (Architect), and epic prioritization (PM) in a single workflow. It produces requirements.md, architecture.md, and epics.md simultaneously, addressing both product and technical dimensions.
Interactive Q&A structures your thinking through targeted questions from three perspectives, then auto-generates template-driven documents populated with your responses. This eliminates context-switching and redundant rewrites, cutting token usage significantly while ensuring alignment across requirements, architecture, and epics.
The Skill creates a compliant directory layout under `planning/<slug>` in your contrib branch, organizing requirements.md, architecture.md, and epics.md in a consistent structure. This standardized layout integrates seamlessly with downstream specification and implementation phases.
Yes. The Skill includes a `--no-commit` flag for testing, allowing you to generate and review all planning documents before they're committed to your contrib branch, giving you control over validation before repository integration.
fabiolpgomesGenerate structured user stories from PRDs and manage local git branches.
mietheGenerate PRDs and phased implementation plans with subagent assignments.
devCharuzuOrganize Agile backlog management and sprint execution with user stories and capacity planning.
pradyumnasagarGuide authors through creating and validating ORS SKILL.md files.