Prompt file imported from rhixecompany/sandbox (.github/prompts/planning/hermes-breakdown-feature-implementation/hermes-breakdown-feature-implementation.prompt.md). Copyright stays with the author.

Table of Contents

Goal

Turns a feature PRD into an implementation plan that an engineering team can execute.

Context

Phases

Table of Contents

• Goal

• Context

• Inputs

• Outputs

• Rules

• Phases

  • Phase 1: Analyze the PRD

• Actions Summary

• Template References

• Personas

• Personality

• Best Practices

• Verification Checklist

• Dependencies

• Subgoals

• Skills Required

• MCP Servers & Tools

• Tasks

• Hooks

• Scripts

• Related Prompts

• Goal

• Context

• Inputs

• Outputs

• Rules

• Phases

• Phase 1: Analyze the PRD

• Actions Summary

• Template References

• Personas

• Personality

• Best Practices

• Verification Checklist

• Dependencies

• Subgoals

• Skills Required

• MCP Servers & Tools

• Tasks

• Hooks

• Scripts

• Related Prompts

Turn a feature PRD into an implementation plan that an engineering team can execute.

• Use when the feature PRD is already available.
• Focus on architecture, data flow, API shape, and delivery considerations.
• Keep the plan grounded in the source PRD and any technical notes.
• Do not omit deployment or security concerns.

Inputs

• Feature PRD path: /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md
• Optional: technical-breakdown.md, implementation constraints

Outputs

• /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md

Rules

Core rules: templates/rules-core.md

1. Keep the plan tied to the PRD requirements.
2. Include architecture, schema, API, frontend, deployment, security, and performance.
3. Use Mermaid where diagrams add clarity.
4. Make the API section concrete with request and response shapes.
5. Surface migration strategy and CI/CD considerations explicitly.
6. Keep the document easy to hand to an engineer.

Phase 1: Analyze the PRD

Goal: extract the technical work implied by the feature.

Actions Summary

1. Read and analyze the feature PRD.
2. Draft the implementation plan structure.
3. Add architecture, schema, API, UI, and delivery notes.
4. Review the draft for completeness and clarity.

Template References

Templates in templates/:- phases.md

Personas

See templates/personas.md for shared persona templates.

Personality

See templates/personality.md for shared personality guidelines.

• Tone: Direct, practical, actionable
• Style: Structured with clear steps and verification
• Avoid: Ambiguity, assumptions, scope creep
• Encourage: Evidence-based decisions, minimal changes

Best Practices

See templates/best-practices.md for cross-cutting best practices.

1. DRY — Reference shared templates instead of duplicating content.
2. Structured output — Use clear sections with consistent heading levels.
3. Verification gates — Always verify before claiming completion.
4. Minimal changes — Fix root cause, not symptoms.

Verification Checklist

Dependencies

See templates/deps-core.md for shared dependency patterns.

Subgoals

1. Prepare — Understand requirements and prerequisites.
2. Execute — Follow structured workflow with incremental progress.
3. Verify — Confirm output meets requirements and standards.
4. Document — Record results, decisions, and lessons learned.

Skills Required

See templates/skills-table-core.md for shared skills table.

MCP Servers & Tools

The following MCP servers and tools are available for this task. Use them in preference to native equivalents per MCP-first tooling policy.

| ast-grep | AST-based code search and replace | | filesystem | File read/write operations | | sequential-thinking | Structured reasoning for complex problems | | fetch | Web page content extraction | | playwright | Browser automation for interactive pages | | github | GitHub API operations |

Tasks

• Understand requirements and scope
• Plan approach and identify resources
• Execute work incrementally
• Verify against acceptance criteria
• Document results and decisions

Hooks

Shared workspace hooks run around this prompt's execution — see .github/hooks/README.md: session-logger, session-auto-commit, governance-audit, pre-exec-validate.sh, post-exec-state-log.py.

Scripts

Prompt-library tooling (see .enhance/):

• .enhance/analyze_prompts.py — prompt-library analyzer (Phase 5/7 gate)
• .enhance/verify_phase3.py, .enhance/fix_class_e.py, .enhance/fix_frontmatter_plan.py — Class C–E repair/verify tooling
• .github/hooks/* — hook implementations referenced in the Hooks section

Related Prompts

Workflow

Same-family prompts:

• hermes-breakdown-epic-arch.prompt.md
• hermes-breakdown-epic-pm.prompt.md
• hermes-breakdown-feature-prd.prompt.md
• hermes-breakdown-plan.prompt.md
• hermes-breakdown-test.prompt.md
• hermes-comprehensive-setup.prompt.md
• hermes-doctor-systematic-debugging.prompt.md

# Prompt template
Execute the workflow defined in this file.