Stop Asking Which Agentic Coding Methodology to Use

A developer argues that the debate over which agentic coding methodology to adopt is misguided, contending that frameworks like Superpowers, BMAD, OpenSpec, SpecKit, GSD, Ralph, and Compound Engineering each orchestrate a distinct layer of AI-assisted development rather than competing as a single winner. The recommended approach is to compose a stack, sequencing BMAD for ambiguous product intent, OpenSpec for durable change contracts, Superpowers for implementation and verification, and Compound Engineering for capturing post-delivery lessons. The developer notes they would personally start with BMAD as a higher-level harness combined with OpenSpec to drive implementation quality.

The prevailing question in AI-assisted development—"Which methodology should I use?"—is fundamentally flawed. Superpowers, BMAD, Compound Engineering, OpenSpec, SpecKit, GSD, Ralph. The ecosystem is flooded with systems claiming to run your AI agents. The thesis here is simple: There is no universal winner. Each framework orchestrates a distinct layer of agentic development. Stop searching for a silver bullet. Build a stack. 1. Execution vs. Intent: Superpowers vs. BMAD The most critical comparison dictates your starting vector. - Superpowers Pure Engineering : Operates as a demanding senior engineer. It enforces design, planning, strict test-driven development, and rigorous review. Default to this for daily coding, solo development, and pure implementation tasks. - BMAD Product Intent : Operates as a complete product organization—analysts, PMs, architects, and readiness gates. Deploy this when product intent remains uncertain or stakeholder complexity is high. 2. Context Retention: OpenSpec vs. SpecKit Both frameworks combat context drift by anchoring requirements in versioned files. - OpenSpec: Optimized for change and brownfield execution. It is the durable change contract for everyday work on real, existing production codebases. - SpecKit: Optimized for governance. It dictates a constitution, traceability, and audit trails. Reserve for heavily regulated environments. 3. The Autonomy Layer: GSD vs. Ralph Tread carefully here. - GSD: Designed to safeguard structured projects across context windows via requirements, roadmaps, and verification. Note: The original repository was archived in June 2026. Use only for long unattended runs once a stable fork emerges. - Ralph: A continuous loop pick an item, implement a test, repeat . Warning: Without impenetrable tests, Ralph will happily burn tokens iterating on bad decisions. 4. The Meta-Layer: Compound Engineering Compound Engineering shifts the focus from "How do we build this correctly?" to "How does this work make the next task frictionless?" Every feature delivery concludes by recording lessons for agents to reuse. If your role leans closer to founder than individual contributor, this is your core methodology. The Winning Synthesis Do not install everything. Orchestrate the right sequence based on the situation: 1. BMAD to define requirements when product intent is ambiguous. 2. OpenSpec to establish a durable change contract in the codebase. 3. Superpowers to drive implementation and rigorous verification. 4. Compound Engineering to extract and record lessons post-delivery. I personally would start with BMAD as a higher level harness, and combine it with OpenSpec to drive quality of implementation to the desired level. Now go build.