e2e
01colliercoder/forge-methodology
Command Claude Code
Run automated E2E browser tests for a FORGE feature, capturing screenshots and generating a comprehensive test report.
A structured feature development pipeline for Claude Code with parallel AI agents for research, validation, and implementation
colliercoder/forge-methodology
Command Claude Code
Run automated E2E browser tests for a FORGE feature, capturing screenshots and generating a comprehensive test report.
colliercoder/forge-methodology
Command Claude Code
Deploy 4 parallel research subagents to analyze a feature before implementation. Creates comprehensive research reports and synthesized BRAINSTORM document.
colliercoder/forge-methodology
Command Claude Code
Validate the implementation with automated tests AND document what was done.
colliercoder/forge-methodology
Command Claude Code
Transform a rough idea into a clear, well-defined feature brief through interactive questioning. Creates a living IDEATION.md document that solidifies what the feature IS and IS NOT.
colliercoder/forge-methodology
Command Claude Code
Initialize the learnings folder structure for a new project or verify existing structure.
colliercoder/forge-methodology
Command Claude Code
Create a comprehensive, foolproof SPEC document from the BRAINSTORM and research reports.
colliercoder/forge-methodology
Command Claude Code
Execute an approved SPEC autonomously using Ralph-style iteration.
colliercoder/forge-methodology
Command Claude Code
Deploy 4 parallel validation subagents to verify the SPEC is complete, accurate, and ready for flawless implementation. Catches issues BEFORE coding begins.
colliercoder/forge-methodology
Command Claude Code
Execute the SPEC with smart implementation - pauses on uncertainty, spawns helper subagents as needed, and writes learnings continuously.
colliercoder/forge-methodology
Command Claude Code
Check the current progress of a feature through the FORGE pipeline.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: