mindforge-add-tests
This Claude Code skill generates unit and end-to-end tests for a completed development phase by analyzing its documentation files (SUMMARY.md, CONTEXT.md, VERIFICATION.md) and implementation code. It classifies files into appropriate test categories, presents a test plan for approval, generates tests following RED-GREEN conventions, and commits them with a standardized message. Use this when a phase implementation is complete and requires comprehensive test coverage aligned with UAT criteria.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-add-tests && cp -r /tmp/mindforge-add-tests/.agent/skills/mindforge-add-tests ~/.claude/skills/mindforge-add-testsSKILL.md
<objective>
Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.
Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
Output: Test files committed with message `test(phase-{N}): add unit and E2E tests from add-tests command`
</objective>
<execution_context>
@.agent/workflows/mindforge-add-tests.md
</execution_context>
<context>
Phase: $ARGUMENTS
@.planning/STATE.md
@.planning/ROADMAP.md
</context>
<process>
Execute the add-tests workflow from @.agent/workflows/mindforge-add-tests.md end-to-end.
Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting).
</process>Publish a skill to the npm registry (or private registry).
Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.