sipherxyz/huli-feature

Huli Feature Implementation Workflow

PRD-driven development using BMGD agents and workflows for UE5.7.1.

Input

Accept one of:

• Document path: claude-agents/s2/*.md or similar
• Inline description: Feature requirements in chat

Output Location

All artifacts go to claude-agents/s2/:

claude-agents/s2/
├── game-brief.md         (Phase 1)
├── gdd.md                (Phase 2)
├── architecture.md       (Phase 3)
├── sprint-status.yaml    (Phase 4)
├── stories/              (Phase 5)
│   ├── story-001.md
│   └── ...
└── implementation-artifacts/

Workflow Phases

Check for existing artifacts before each phase. Skip if valid artifact exists.

Phase 1: Preproduction

Skill: /bmad:bmgd:workflows:create-game-brief
Output: claude-agents/s2/game-brief.md

Skip if game-brief.md exists and matches current feature scope.

Phase 2: Design

Skill: /bmad:bmgd:workflows:gdd
Input: game-brief.md
Output: claude-agents/s2/gdd.md

Phase 3: Technical Architecture

Skill: /bmad:bmgd:workflows:game-architecture
Input: gdd.md
Output: claude-agents/s2/architecture.md

For significant changes, include an Architecture Decision Record in architecture.md:

## Architecture Decision

**Decision:** {One sentence}
**Context:** {Why needed}
**Consequences:** {Trade-offs accepted}

CHECKPOINT: Confirm architecture with user before proceeding.

Phase 4: Sprint Planning

Skill: /bmad:bmgd:workflows:sprint-planning
Input: architecture.md, gdd.md
Output: claude-agents/s2/sprint-status.yaml

Include a file manifest in sprint-status.yaml or architecture.md:

| File | Change Type | Tasks | |------|-------------|-------| | {Path} | New/Modify/Delete | 1, 2 |

Phase 5: Story Creation (Loop)

Skill: /bmad:bmgd:workflows:create-story
Output: claude-agents/s2/stories/story-NNN.md

Repeat until all stories from sprint-status.yaml are created.

Task Ordering Rules — order stories/tasks so that:

1. Headers before implementation
2. Base classes before derived
3. Data structures before logic
4. Core functionality before edge cases
5. Each task is independently committable

Each story should include per-task file lists and verification checklists:

### Task N: {Title}

**Files:**
- `{Path/File.h}` - [New/Modify]
- `{Path/File.cpp}` - [New/Modify]

**Changes:**
1. {Specific change}

**Dependencies:** None | Task N
**Complexity:** S/M/L

**Verification:**
- [ ] Compiles without warnings
- [ ] {Specific verification}

CHECKPOINT: Review stories with user before development.

Phase 6: Development (Loop per Story)

Skill: /bmad:bmgd:workflows:dev-story
Input: stories/story-NNN.md
Output: Source code in Plugins/

Execute each story in priority order from sprint-status.yaml.

Phase 7: Build

Skill: /dev-workflow:ue-cpp-build

Compile and fix errors. Do NOT auto-run - wait for user to verify.

CHECKPOINT: Confirm build success before review.

Phase 8: Code Review (3x Adversarial)

Skill: /bmad:bmgd:workflows:code-review

Run 3 times for thorough adversarial review. Each pass should find issues.

Phase 9: Automated Tests

Skill: /bmad:bmgd:workflows:gametest-automate

Generate and run tests for implemented features.

Test Strategy — ensure coverage includes:

• Automated: Unit tests for core logic
• Manual: PIE verification of behavior

## Test Strategy

### Automated
- [ ] Unit test for {core logic}

### Manual
- [ ] PIE verification of {behavior}

Phase 10: Delivery

git checkout -b feature/<short-slug>
git add <changed-files>
git commit -m "<conventional-commit>"
git push -u origin feature/<short-slug>
gh pr create --title "<feature>" --body "..."

Phase Skip Rules

| Artifact | Skip Condition | |----------|----------------| | game-brief.md | Exists and covers feature scope | | gdd.md | Exists and references current brief | | architecture.md | Exists and matches gdd | | sprint-status.yaml | Exists with valid stories | | stories/*.md | Individual story exists |

When resuming, read sprint-status.yaml to determine current phase.

Example Usage

User: Implement companion state tree refactor from PRD
Claude:
1. Check claude-agents/s2/ for existing artifacts
2. Resume from last completed phase
3. Execute remaining phases with checkpoints

Plan Save Location

Implementation plans can also be saved to claude-agents/ugm/plans/{feature}-plan.md when used outside the full BMGD pipeline (e.g., triggered via "plan implementation" or "break down tasks").

Error Handling

• Build failures: Fix and retry, don't skip
• Review findings: Address before proceeding
• Test failures: Fix implementation, re-run tests

Legacy Metadata

skill: huli-feature
invoke: /dev-workflow:huli-feature