[{"data":1,"prerenderedAt":1399},["ShallowReactive",2],{"navigation_docs":3,"blog-posts":137},[4,28,62,94,100,133],{"title":5,"path":6,"stem":7,"children":8,"order":11,"icon":27},"Getting Started","/getting-started","1.getting-started/index",[9,12,17,22],{"title":10,"path":6,"stem":7,"order":11},"What is Gangsta Agents?",1,{"title":13,"path":14,"stem":15,"order":16},"Installation","/getting-started/installation","1.getting-started/installation",2,{"title":18,"path":19,"stem":20,"order":21},"Quickstart — Your First Heist","/getting-started/quickstart","1.getting-started/quickstart",3,{"title":23,"path":24,"stem":25,"order":26},"The 1% Rule","/getting-started/the-1-percent-rule","1.getting-started/the-1-percent-rule",4,"i-lucide-rocket",{"title":29,"path":30,"stem":31,"children":32,"order":11,"icon":61},"Core Concepts","/core-concepts","2.core-concepts/index",[33,34,39,43,48,52,56],{"title":29,"path":30,"stem":31,"order":11},{"title":35,"path":36,"stem":37,"order":38},"Intent Routing","/core-concepts/intent-routing","2.core-concepts/intent-routing",5,{"title":40,"path":41,"stem":42,"order":26},"Omerta — The Five Laws","/core-concepts/omerta","2.core-concepts/omerta",{"title":44,"path":45,"stem":46,"order":47},"Spec-Driven Development","/core-concepts/spec-driven-dev","2.core-concepts/spec-driven-dev",7,{"title":49,"path":50,"stem":51,"order":16},"The Gangsta Agents Family Hierarchy","/core-concepts/the-borgata","2.core-concepts/the-borgata",{"title":53,"path":54,"stem":55,"order":21},"The Heist Pipeline","/core-concepts/the-heist","2.core-concepts/the-heist",{"title":57,"path":58,"stem":59,"order":60},"The Ledger","/core-concepts/the-ledger","2.core-concepts/the-ledger",6,"i-lucide-brain",{"title":63,"icon":64,"path":65,"stem":66,"children":67},"Heist Pipeline","i-lucide-workflow","/heist-pipeline","3.heist-pipeline",[68,70,74,78,82,86,90],{"title":53,"path":65,"stem":69,"order":11},"3.heist-pipeline/index",{"title":71,"path":72,"stem":73,"order":16},"Reconnaissance","/heist-pipeline/reconnaissance","3.heist-pipeline/1.reconnaissance",{"title":75,"path":76,"stem":77,"order":21},"The Grilling","/heist-pipeline/the-grilling","3.heist-pipeline/2.the-grilling",{"title":79,"path":80,"stem":81,"order":26},"The Sit-Down","/heist-pipeline/the-sit-down","3.heist-pipeline/3.the-sit-down",{"title":83,"path":84,"stem":85,"order":38},"Resource Development","/heist-pipeline/resource-development","3.heist-pipeline/4.resource-development",{"title":87,"path":88,"stem":89,"order":60},"Execution","/heist-pipeline/the-hit","3.heist-pipeline/5.the-hit",{"title":91,"path":92,"stem":93,"order":47},"The Delivery","/heist-pipeline/laundering","3.heist-pipeline/6.laundering",{"title":95,"path":96,"stem":97,"children":98},"Skills Reference","/skills","4.skills/index",[99],{"title":95,"path":96,"stem":97},{"title":101,"icon":102,"path":103,"stem":104,"children":105},"Advanced","i-lucide-zap","/advanced","5.advanced",[106,109,113,117,121,125,129],{"title":107,"path":103,"stem":108,"order":11},"Advanced Topics","5.advanced/index",{"title":110,"path":111,"stem":112,"order":38},"Artifacts Reference","/advanced/artifacts","5.advanced/artifacts",{"title":114,"path":115,"stem":116,"order":60},"Autonomous Mode","/advanced/autonomous-mode","5.advanced/autonomous-mode",{"title":118,"path":119,"stem":120,"order":26},"Checkpoint Recovery","/advanced/checkpoint-recovery","5.advanced/checkpoint-recovery",{"title":122,"path":123,"stem":124,"order":38},"Contributing","/advanced/contributing","5.advanced/contributing",{"title":126,"path":127,"stem":128,"order":16},"Writing Custom Skills","/advanced/custom-skills","5.advanced/custom-skills",{"title":130,"path":131,"stem":132,"order":21},"Multi-Agent Patterns","/advanced/multi-agent-patterns","5.advanced/multi-agent-patterns",{"title":134,"path":135,"stem":136,"order":60},"Glossary","/glossary","6.glossary",[138,1198],{"id":139,"title":140,"body":141,"description":1188,"extension":1189,"links":1190,"meta":1191,"navigation":1193,"path":1194,"seo":1195,"stem":1196,"__hash__":1197},"docs/blog/2026-05-01-sdd-compared.md","Spec-Driven Development in 2026",{"type":142,"value":143,"toc":1170},"minimark",[144,148,151,154,189,192,198,201,206,219,222,227,243,246,272,275,280,290,295,315,320,334,340,345,347,351,367,370,374,377,383,386,392,399,413,417,437,441,455,460,465,467,471,481,484,488,491,517,524,530,536,542,545,549,572,576,584,589,594,596,600,614,617,620,631,637,642,727,733,738,745,749,752,758,761,765,798,802,805,809,812,856,863,869,873,896,900,911,916,921,923,927,931,934,964,968,972,976,1060,1067,1069,1073,1076,1082,1085,1091,1094,1097,1123,1126,1128,1137,1147,1160],[145,146,147],"p",{},"Ask Claude or Copilot to \"add user authentication\" and you'll get something. Whether that something matches what you actually need depends on twenty silent inferences the agent made: which auth pattern, which session strategy, which security level, which error handling. None of them written down. None of them reviewable. All of them yours to debug later.",[145,149,150],{},"This is the structural failure SDD addresses. But \"spec-first\" is one principle implemented four very different ways. GitHub Spec Kit, OpenSpec, BMad Method, and Gangsta Agents agree that the spec comes before the code — they disagree on almost everything else: how strict the gates are, where the spec lives, whether agents debate, whether memory persists across sessions.",[145,152,153],{},"I'll compare them across five axes that actually matter in practice:",[155,156,157,165,171,177,183],"ul",{},[158,159,160,164],"li",{},[161,162,163],"strong",{},"Spec scope"," — feature-level (one change) or project-level (the whole project)",[158,166,167,170],{},[161,168,169],{},"Adversarial review"," — is there a mechanism that attacks a proposal before code is written",[158,172,173,176],{},[161,174,175],{},"Gate strictness"," — can the agent proceed without explicit human approval",[158,178,179,182],{},[161,180,181],{},"Institutional memory"," — is experience preserved between sessions",[158,184,185,188],{},[161,186,187],{},"Cost of entry"," — dependencies, setup time, learning curve",[145,190,191],{},"Ecosystem metrics (stars, community, extensions) live in a separate table — they're useful, but they're not architecture.",[145,193,194],{},[195,196,197],"em",{},"Disclosure: I built Gangsta Agents. It's included for completeness, not promotion. Judge for yourself.",[199,200],"hr",{},[202,203,205],"h2",{"id":204},"github-spec-kit","GitHub Spec Kit",[145,207,208,211,212],{},[161,209,210],{},"88k stars"," | ",[213,214,218],"a",{"href":215,"rel":216},"https://github.com/github/spec-kit",[217],"nofollow","github.com/github/spec-kit",[145,220,221],{},"Official open-source project from GitHub, launched in 2025, with an active ecosystem of extensions and presets.",[145,223,224],{},[161,225,226],{},"How it works:",[145,228,229,230,234,235,238,239,242],{},"Four phases with clear artifacts: Constitution → Specify → Plan → Tasks → Implement. Each phase is triggered via slash commands (",[231,232,233],"code",{},"/speckit.constitution",", ",[231,236,237],{},"/speckit.specify",", etc.) or agent skills. ",[231,240,241],{},"Constitution.md"," is an immutable document with project principles.",[145,244,245],{},"Each phase is a handoff between the human (driving intent) and the AI (doing the writing). You don't move to the next phase until the current artifact is reviewed and accepted:",[155,247,248,254,260,266],{},[158,249,250,253],{},[161,251,252],{},"Specify"," — the developer writes what needs to be built and why. The AI generates a detailed spec covering user stories, acceptance criteria, workflows, and success metrics. No code, no implementation details.",[158,255,256,259],{},[161,257,258],{},"Plan"," — the developer adds technical constraints (tech stack, architecture, compliance, performance). The AI produces a technical plan that respects those constraints. Alternative plans can be generated for comparison.",[158,261,262,265],{},[161,263,264],{},"Tasks"," — the AI breaks work into small reviewable units. Each task is concrete and independently verifiable (\"Create a user registration endpoint that validates email format\" — not \"build authentication\").",[158,267,268,271],{},[161,269,270],{},"Implement"," — the AI executes each task. Code changes are traceable to specific requirements, not to a giant diff with unclear intent.",[145,273,274],{},"The structure is the value. Each phase has a checkpoint where humans catch misalignment before it becomes rework.",[145,276,277],{},[161,278,279],{},"Real workflow:",[281,282,287],"pre",{"className":283,"code":285,"language":286},[284],"language-text","/speckit.constitution  Create principles focused on code quality and testing standards\n/speckit.specify       Build a Kanban board with drag-and-drop, multiple users, no login\n/speckit.plan          Use .NET Aspire, Postgres, Blazor server\n/speckit.tasks\n/speckit.implement\n","text",[231,288,285],{"__ignoreMap":289},"",[145,291,292],{},[161,293,294],{},"Strengths:",[155,296,297,300,303,306,309,312],{},[158,298,299],{},"50+ community extensions: Jira, Azure DevOps, GitHub Issues, worktrees, security review, V-Model, and more",[158,301,302],{},"Presets for customization without touching the core",[158,304,305],{},"Works with 28 AI agents: Claude Code, Gemini CLI, Copilot, Cursor, OpenCode, Codex, Kiro, Windsurf, and others",[158,307,308],{},"Ralph Loop — autonomous execution cycle for fully agentic implementation",[158,310,311],{},"Brownfield bootstrap extension for existing projects",[158,313,314],{},"Enterprise-ready: Azure DevOps, Jira integrations, compliance requirements",[145,316,317],{},[161,318,319],{},"Weaknesses:",[155,321,322,325,328,331],{},[158,323,324],{},"Heavyweight: requires Python, uv, git",[158,326,327],{},"Phase gates exist but aren't strict — agent can continue without explicit approval",[158,329,330],{},"No adversarial review out of the box (extension only)",[158,332,333],{},"Spec lives at feature level, not project level",[145,335,336,339],{},[161,337,338],{},"Best for:"," If you already have Jira or Azure DevOps and need compatibility with your existing process — Spec Kit brings SDD without changing infrastructure.",[145,341,342],{},[195,343,344],{},"Spec Kit is the most polished, most extensible, and most enterprise-ready of the four — but it pays for that with weight and bypassable gates.",[199,346],{},[202,348,350],{"id":349},"openspec","OpenSpec",[145,352,353,211,356,211,361,366],{},[161,354,355],{},"37.7k stars",[213,357,360],{"href":358,"rel":359},"https://github.com/Fission-AI/OpenSpec",[217],"github.com/Fission-AI/OpenSpec",[213,362,365],{"href":363,"rel":364},"https://openspec.dev",[217],"openspec.dev"," | YC W26",[145,368,369],{},"Built by Tabish (@0xTab), YC W26. Philosophy: fluid, not rigid. Iterative, not waterfall.",[145,371,372],{},[161,373,226],{},[145,375,376],{},"Two key actions:",[281,378,381],{"className":379,"code":380,"language":286},[284],"/opsx:propose \"add dark mode\"\n→ creates openspec/changes/add-dark-mode/\n  ✓ proposal.md  — why and what changes\n  ✓ specs/       — requirements and scenarios\n  ✓ design.md    — technical approach\n  ✓ tasks.md     — implementation checklist\n\n/opsx:apply\n→ executes all tasks\n",[231,382,380],{"__ignoreMap":289},[145,384,385],{},"Each change lives in its own folder. Artifacts can be updated at any time — no strict phase transitions.",[145,387,388,391],{},[161,389,390],{},"Spec deltas"," — unique to OpenSpec. Every change produces a diff against the existing spec, not a new document. Reviewers see exactly what's changing in the requirements (added scenarios, modified behaviors, deleted constraints) before any code is written.",[145,393,394,395,398],{},"Example: adding \"Remember me\" to authentication produces a delta showing the new scenario added to ",[231,396,397],{},"auth-session/spec.md",", not a fresh spec file.",[145,400,401,402,405,406,234,409,412],{},"Specs live in the codebase as permanent documentation. Other frameworks treat the spec as planning material that gets discarded after implementation. OpenSpec keeps specs in ",[231,403,404],{},"openspec/specs/"," organized by capability (",[231,407,408],{},"auth-login/",[231,410,411],{},"checkout-cart/","). When a new developer joins, they read the specs to understand what the code is supposed to do — not what it currently does.",[145,414,415],{},[161,416,294],{},[155,418,419,425,428,431,434],{},[158,420,421,422],{},"Minimal overhead: ",[231,423,424],{},"npm install -g @fission-ai/openspec",[158,426,427],{},"Brownfield-first — built for working with existing code",[158,429,430],{},"Iterative approach: spec evolves with the code",[158,432,433],{},"Active community: Discord, 37.7k stars",[158,435,436],{},"Works with 20+ tools",[145,438,439],{},[161,440,319],{},[155,442,443,446,449,452],{},[158,444,445],{},"Fluid means less structure — no strict gates",[158,447,448],{},"No adversarial review",[158,450,451],{},"No institutional memory between sessions",[158,453,454],{},"Spec quality is entirely on the developer",[145,456,457,459],{},[161,458,338],{}," If you want to try SDD today in 5 minutes on an existing project — this is the fastest start of the four.",[145,461,462],{},[195,463,464],{},"OpenSpec treats specs as living code documentation through deltas — the lightest framework here, but you carry the discipline yourself.",[199,466],{},[202,468,470],{"id":469},"bmad-method","BMad Method",[145,472,473,211,476],{},[161,474,475],{},"44.2k stars",[213,477,480],{"href":478,"rel":479},"https://github.com/bmad-code-org/BMAD-METHOD",[217],"github.com/bmad-code-org/BMAD-METHOD",[145,482,483],{},"Full AI-driven framework for the entire development lifecycle — from idea to shipped code. Version 6, actively maintained.",[145,485,486],{},[161,487,226],{},[145,489,490],{},"Specialized named agents guide the project through each phase. Modular architecture — extendable via BMad Builder. Four phases, each producing artifacts that feed the next:",[155,492,493,499,505,511],{},[158,494,495,498],{},[161,496,497],{},"Analysis"," (optional) — brainstorming, domain/market/technical research, product brief. Validates the idea before committing to planning.",[158,500,501,504],{},[161,502,503],{},"Planning"," — PRD with functional and non-functional requirements + UX spec when relevant.",[158,506,507,510],{},[161,508,509],{},"Solutioning"," — architecture document with ADRs, epics broken into stories, and an Implementation Readiness Check that produces a formal gate: PASS / CONCERNS / FAIL.",[158,512,513,516],{},[161,514,515],{},"Implementation"," — sprint planning, story-by-story development, code review, retrospective.",[145,518,519,520,523],{},"For small well-understood work, Quick Flow (",[231,521,522],{},"bmad-quick-dev",") skips phases 1–3 entirely — clarify intent, plan, implement, review in one unified pass.",[145,525,526,529],{},[231,527,528],{},"project-context.md"," — BMad's equivalent of Constitution. A document that captures technology stack, implementation rules, and project conventions. Generated from architecture or codebase, it guides every workflow.",[145,531,532,535],{},[161,533,534],{},"Adversarial Review"," is the recurring quality mechanism, used across the whole pipeline — code review, implementation readiness checks, spec validation. The reviewer agent must find issues — zero findings triggers a halt and re-analysis. The reviewer assumes problems exist and must surface them. Output is structured by severity:",[281,537,540],{"className":538,"code":539,"language":286},[284],"- HIGH   - login.ts:47 - No rate limiting on failed attempts\n- HIGH   - Session token stored in localStorage (XSS vulnerable)\n- MEDIUM - Password validation happens client-side only\n- LOW    - Magic number 3600 should be SESSION_TIMEOUT_SECONDS\n",[231,541,539],{"__ignoreMap":289},[145,543,544],{},"Unlike Gangsta, there is no Nash Equilibrium as a stopping condition — the debate ends at the orchestrator's discretion. Human filtering is required: because the AI is instructed to find problems, false positives are expected. You decide what is real.",[145,546,547],{},[161,548,294],{},[155,550,551,554,557,560,563,566,569],{},[158,552,553],{},"Covers the full lifecycle: analysis → planning → implementation → verification",[158,555,556],{},"12+ specialized named agents (PM, Architect, Developer, UX, Scrum Master, and more)",[158,558,559],{},"Adversarial Review as a built-in feature",[158,561,562],{},"Supports Agile-compatible workflows — iterative sprints, user stories, backlog",[158,564,565],{},"Large community: Discord, YouTube, active GitHub",[158,567,568],{},"Domain-specific modules: Game Dev Studio, Creative Intelligence Suite, Test Architect",[158,570,571],{},"Works with Claude Code, Cursor, Codex CLI",[145,573,574],{},[161,575,319],{},[155,577,578,581],{},[158,579,580],{},"High entry barrier — many concepts to learn upfront",[158,582,583],{},"Quality depends on installed modules (same applies to Spec Kit with its extensions)",[145,585,586,588],{},[161,587,338],{}," If you're building a new product from scratch and want AI at every stage from idea to deployment — BMad covers the full cycle.",[145,590,591],{},[195,592,593],{},"BMad is the only framework that pairs full-lifecycle coverage with a built-in adversarial reviewer — pay the entry cost only if you'll use the whole pipeline.",[199,595],{},[202,597,599],{"id":598},"gangsta-agents","Gangsta Agents",[145,601,602,211,609],{},[161,603,604],{},[213,605,608],{"href":606,"rel":607},"https://github.com/kucherenko/gangsta",[217],"github.com/kucherenko/gangsta",[213,610,613],{"href":611,"rel":612},"https://gangsta.page",[217],"gangsta.page",[145,615,616],{},"Agentic framework for spec-driven development built on the organizational model of the mafia. Zero dependencies, installs in one step. The newest entry of the four — first stable release v1.1.1 in April 2026 — so the comparison reflects an early-stage project rather than an established ecosystem.",[145,618,619],{},"Gangsta is built on the principle of strict hierarchy and explicit gates — every decision is traceable to the contract, every agent answers only to its own level.",[145,621,622,623,626,627,630],{},"Gangsta supports two modes: ",[161,624,625],{},"manual mode"," where the Don approves every phase gate, and ",[161,628,629],{},"autonomous mode"," where the entire pipeline runs end-to-end without human intervention. Choose based on the cost of failure for the task at hand.",[632,633],"img",{"src":634,"alt":635,"style":636},"/pipeline-flow.svg","The Gangsta Agents Heist Pipeline — 6 phases with Don-approved gates","width:100%;border-radius:4px;margin:1.5rem 0 2rem;",[145,638,639],{},[161,640,641],{},"How it works — 6-phase Heist Pipeline:",[643,644,645,661],"table",{},[646,647,648],"thead",{},[649,650,651,655,658],"tr",{},[652,653,654],"th",{},"Phase",[652,656,657],{},"What happens",[652,659,660],{},"Gate",[662,663,664,675,685,695,705,716],"tbody",{},[649,665,666,669,672],{},[667,668,71],"td",{},[667,670,671],{},"Agents scan the codebase, read the Ledger",[667,673,674],{},"Don approves Dossier",[649,676,677,679,682],{},[667,678,75],{},[667,680,681],{},"Adversarial debate: Proposer vs Devils-Advocate, min 2 rounds",[667,683,684],{},"Don approves consensus",[649,686,687,689,692],{},[667,688,79],{},[667,690,691],{},"Formal contract — no code allowed",[667,693,694],{},"Don signs",[649,696,697,699,702],{},[667,698,83],{},[667,700,701],{},"Decomposition into Work Packages",[667,703,704],{},"Don approves War Plan",[649,706,707,710,713],{},[667,708,709],{},"The Hit",[667,711,712],{},"Parallel execution, TDD mandatory",[667,714,715],{},"Don approves completion",[649,717,718,721,724],{},[667,719,720],{},"Laundering",[667,722,723],{},"Verification, integration, Ledger update",[667,725,726],{},"Don declares Heist complete",[145,728,729,732],{},[161,730,731],{},"Strict hierarchy:"," Don (you) → Consigliere → Underboss → Capo → Soldier. No horizontal communication — only through the chain of command.",[734,735,737],"h3",{"id":736},"the-grilling-unique-feature","The Grilling — unique feature",[145,739,740,741,744],{},"Before any spec is written, three agents debate the solution: Proposer proposes the architecture, Devils-Advocate attacks (vulnerabilities, constitution violations, regression risks), Synthesizer integrates valid attacks and the Don's feedback. Minimum 2 rounds, maximum 7, exit only at ",[161,742,743],{},"Nash Equilibrium"," — when the Devils-Advocate can't raise a single new valid objection.",[734,746,748],{"id":747},"the-sit-down-real-example","The Sit-Down — real example",[145,750,751],{},"Here's a fragment from a real contract in gangsta-money-tracker-example:",[281,753,756],{"className":754,"code":755,"language":286},[284],"## Functional Requirements\n- FR-001: Every transaction stores amount in original currency\n- FR-002: Every transaction stores amount_default in home currency\n- FR-003: Every transaction stores exchange_rate at create time\n- FR-008: Changing default currency recalculates ALL existing transactions\n\n## Architectural Decisions\n- AD-001: Integer storage — no float rounding errors\n- AD-002: Currencies table in DB, not hardcoded enum\n- AD-005: Rate stored per-transaction, not computed at query time\n  (exchange rates change; the rate at transaction time is correct)\n",[231,757,755],{"__ignoreMap":289},[145,759,760],{},"No code. Just WHAT and WHY.",[734,762,764],{"id":763},"governance-through-omerta-5-laws","Governance through Omerta — 5 laws:",[766,767,768,774,780,786,792],"ol",{},[158,769,770,773],{},[161,771,772],{},"Introduction Rule"," — no agent-to-agent communication without hierarchy mediation",[158,775,776,779],{},[161,777,778],{},"Rule of Availability"," — all state saved to files before every phase transition",[158,781,782,785],{},[161,783,784],{},"Rule of Truth"," — every claim cites its source. No citation — stronzate",[158,787,788,791],{},[161,789,790],{},"Rule of Tribute"," — token and resource budgets are enforced",[158,793,794,797],{},[161,795,796],{},"Spec is Law"," — if code contradicts the spec, the spec is revised. Never the reverse.",[734,799,801],{"id":800},"institutional-memory","Institutional Memory",[145,803,804],{},"Gangsta stores history in the filesystem. After each Heist the Ledger is updated: successful patterns become Commandments, failures become Negative Constraints in the Constitution. During Reconnaissance, Associates scan the Ledger and include relevant entries in the next Heist's Dossier.",[734,806,808],{"id":807},"dev-skills-separate-toolkit","Dev Skills — separate toolkit",[145,810,811],{},"Beyond the Heist Pipeline, Gangsta ships 7 software development skills that can be invoked anywhere:",[155,813,814,820,826,832,838,844,850],{},[158,815,816,819],{},[161,817,818],{},"Interrogation"," — systematic debugging, finds the root cause before applying fixes",[158,821,822,825],{},[161,823,824],{},"The Drill"," — TDD enforcement, no production code without a failing test first",[158,827,828,831],{},[161,829,830],{},"Safehouse"," — git worktrees, isolated operational bases for parallel work",[158,833,834,837],{},[161,835,836],{},"The Audit"," — code review with adversarial framing",[158,839,840,843],{},[161,841,842],{},"Receiving Orders"," — processes user feedback with rigor, not blind agreement",[158,845,846,849],{},[161,847,848],{},"The Sweep"," — verification through evidence, not assumption",[158,851,852,855],{},[161,853,854],{},"Exit Strategy"," — clean branch integration and cleanup",[145,857,858,859,862],{},"The ",[161,860,861],{},"1% Rule"," governs invocation: if there's even a 1% chance a skill applies, you invoke it. No rationalizing, no shortcuts. This prevents the \"quick fix\" mentality that compounds into technical debt.",[145,864,865,868],{},[161,866,867],{},"Lightweight Heist"," for minor fixes: the full 6-phase pipeline isn't always required. For minor fixes or known patterns, a lightweight version skips early phases. For new features, architectural changes, or non-trivial bugs — the full pipeline runs.",[145,870,871],{},[161,872,294],{},[155,874,875,878,881,884,887,890],{},[158,876,877],{},"The Grilling — the only adversarial debate with Nash Equilibrium and fixed rounds",[158,879,880],{},"Strict gates in manual mode — every phase requires explicit Don approval",[158,882,883],{},"Institutional Memory via Ledger",[158,885,886],{},"Zero dependencies — pure Markdown and shell scripts",[158,888,889],{},"TDD enforced at the architecture level",[158,891,892,893],{},"Native integration: Claude Code, GitHub Copilot, Gemini CLI, OpenCode, Codex. Cursor support via ",[231,894,895],{},"npx skills add",[145,897,898],{},[161,899,319],{},[155,901,902,905,908],{},[158,903,904],{},"Steep learning curve due to metaphors and hierarchy",[158,906,907],{},"6-phase pipeline with gates is overkill for isolated single-agent tasks",[158,909,910],{},"Young project, community still forming",[145,912,913,915],{},[161,914,338],{}," If the cost of failure is high, the feature touches multiple domains, and you need full traceability of every decision back to the contract — Gangsta gives the strictest process of the four.",[145,917,918],{},[195,919,920],{},"Gangsta Agents trades ceremony for traceability — the only framework with Nash Equilibrium debate and institutional memory, but the youngest of the four.",[199,922],{},[202,924,926],{"id":925},"comparison","Comparison",[734,928,930],{"id":929},"autonomous-execution-where-the-control-boundary-sits","Autonomous execution: where the control boundary sits",[145,932,933],{},"All four frameworks support autonomous execution — but the human control boundary differs:",[155,935,936,946,952,958],{},[158,937,938,941,942,945],{},[161,939,940],{},"GitHub Spec Kit — Ralph Loop:"," agent takes ",[231,943,944],{},"tasks.md"," and executes all tasks without stopping. Gates can be bypassed.",[158,947,948,951],{},[161,949,950],{},"OpenSpec — /opsx:apply:"," executes all tasks sequentially. Minimal gates, maximum autonomy.",[158,953,954,957],{},[161,955,956],{},"BMad Method — Orchestrator:"," orchestrator agent guides execution through phases. Adversarial review built in, but no named loop.",[158,959,960,963],{},[161,961,962],{},"Gangsta Agents — Two modes:"," in manual mode, Soldiers execute Work Packages with strict gates before and after the phase; in autonomous mode, the entire 6-phase pipeline runs end-to-end without human approval.",[734,965,967],{"id":966},"technical-characteristics","Technical characteristics",[632,969],{"src":970,"alt":971,"style":636},"/tech.jpeg","Technical characteristics comparison across four SDD frameworks",[734,973,975],{"id":974},"ecosystem","Ecosystem",[643,977,978,993],{},[646,979,980],{},[649,981,982,984,986,988,990],{},[652,983],{},[652,985,205],{},[652,987,350],{},[652,989,470],{},[652,991,992],{},"Gangsta",[662,994,995,1012,1027,1043],{},[649,996,997,1000,1003,1006,1009],{},[667,998,999],{},"GitHub stars",[667,1001,1002],{},"88k",[667,1004,1005],{},"37.7k",[667,1007,1008],{},"44.2k",[667,1010,1011],{},"—",[649,1013,1014,1017,1020,1022,1025],{},[667,1015,1016],{},"Extensions",[667,1018,1019],{},"50+",[667,1021,1011],{},[667,1023,1024],{},"Modules",[667,1026,1011],{},[649,1028,1029,1032,1035,1038,1040],{},[667,1030,1031],{},"Community",[667,1033,1034],{},"Large",[667,1036,1037],{},"Growing",[667,1039,1034],{},[667,1041,1042],{},"Forming",[649,1044,1045,1048,1051,1054,1057],{},[667,1046,1047],{},"AI agents",[667,1049,1050],{},"28",[667,1052,1053],{},"20+",[667,1055,1056],{},"12+",[667,1058,1059],{},"5+",[145,1061,1062,1063,1066],{},"Gangsta's Agile compatibility is low ",[161,1064,1065],{},"by design",": each phase requires explicit human approval before proceeding, which conflicts with sprint-based iteration. This is optimized for traceability, not throughput.",[199,1068],{},[202,1070,1072],{"id":1071},"what-all-four-share","What all four share",[145,1074,1075],{},"Despite different approaches, all four frameworks agree on one thing:",[145,1077,1078,1081],{},[161,1079,1080],{},"The human stays in the loop"," — but not for everything. The agent acts on the rules and only stops where a human is actually needed: conflicting requirements, an architectural choice with real consequences, ambiguity affecting the system boundary.",[145,1083,1084],{},"Uncertainty doesn't disappear into confident-sounding text — it gets logged explicitly.",[145,1086,1087,1090],{},[161,1088,1089],{},"Agent context matters more than agent capability."," When Andrej Karpathy named vibe coding in February 2025, the conversation focused on whether models were good enough. Two years later it's clear: the bottleneck isn't model capability. It's that the model has no contract.",[145,1092,1093],{},"SDD does not guarantee correct decisions and does not replace architectural thinking. It reduces the probability of two specific failure modes: agents drifting off-spec due to missing constraints, and contradictions accumulating silently across sessions.",[145,1095,1096],{},"The four frameworks sit on a spectrum from low ceremony to high traceability:",[155,1098,1099,1105,1111,1117],{},[158,1100,1101,1104],{},[161,1102,1103],{},"OpenSpec:"," minimal structure, maximum iteration speed, no gates",[158,1106,1107,1110],{},[161,1108,1109],{},"Spec Kit:"," structured phases, enterprise integrations, bypassable gates",[158,1112,1113,1116],{},[161,1114,1115],{},"BMad:"," full lifecycle, adversarial review, orchestrator-controlled flow",[158,1118,1119,1122],{},[161,1120,1121],{},"Gangsta Agents:"," strict gates at every phase, Nash Equilibrium debate, institutional memory",[145,1124,1125],{},"Pick based on your failure cost and change velocity. Higher failure cost requires stricter gates. Higher change velocity requires lower ceremony.",[199,1127],{},[145,1129,1130,1133,1134],{},[161,1131,1132],{},"GitHub Spec Kit:"," ",[213,1135,218],{"href":215,"rel":1136},[217],[145,1138,1139,1133,1141,211,1144],{},[161,1140,1103],{},[213,1142,360],{"href":358,"rel":1143},[217],[213,1145,365],{"href":363,"rel":1146},[217],[145,1148,1149,1133,1152,211,1155],{},[161,1150,1151],{},"BMad Method:",[213,1153,480],{"href":478,"rel":1154},[217],[213,1156,1159],{"href":1157,"rel":1158},"https://docs.bmad-method.org",[217],"docs.bmad-method.org",[145,1161,1162,1133,1164,211,1167],{},[161,1163,1121],{},[213,1165,608],{"href":606,"rel":1166},[217],[213,1168,613],{"href":611,"rel":1169},[217],{"title":289,"searchDepth":16,"depth":16,"links":1171},[1172,1173,1174,1175,1182,1187],{"id":204,"depth":16,"text":205},{"id":349,"depth":16,"text":350},{"id":469,"depth":16,"text":470},{"id":598,"depth":16,"text":599,"children":1176},[1177,1178,1179,1180,1181],{"id":736,"depth":21,"text":737},{"id":747,"depth":21,"text":748},{"id":763,"depth":21,"text":764},{"id":800,"depth":21,"text":801},{"id":807,"depth":21,"text":808},{"id":925,"depth":16,"text":926,"children":1183},[1184,1185,1186],{"id":929,"depth":21,"text":930},{"id":966,"depth":21,"text":967},{"id":974,"depth":21,"text":975},{"id":1071,"depth":16,"text":1072},"GitHub Spec Kit, OpenSpec, BMad Method, and Gangsta Agents all implement spec-first development but with different philosophies. Here's how they actually differ — and how to choose.","md",null,{"date":1192},"2026-05-01",false,"/blog/2026-05-01-sdd-compared",{"title":140,"description":1188},"blog/2026-05-01-sdd-compared","9pM1tRI5uOO8K51WGO0MNgc-J789YGqH_c9jGfk9D3Q",{"id":1199,"title":1200,"body":1201,"description":1392,"extension":1189,"links":1190,"meta":1393,"navigation":1193,"path":1395,"seo":1396,"stem":1397,"__hash__":1398},"docs/blog/2026-04-18-the-family-vs-the-team.md","The Family vs. The Team",{"type":142,"value":1202,"toc":1384},[1203,1237,1241,1244,1247,1251,1254,1261,1264,1267,1271,1275,1281,1284,1294,1297,1301,1304,1307,1310,1312,1315,1319,1325,1328,1331,1342,1346,1349,1356,1359,1363,1366,1369,1376,1379],[1204,1205,1207,1208,1207,1214,1207,1220],"div",{"style":1206},"display:flex;align-items:center;gap:1.5rem;padding:1.25rem 1.5rem;background:var(--site-surface);border:1px solid var(--site-border);border-radius:0.75rem;margin-bottom:2.75rem;","\n  ",[632,1209],{"src":1210,"alt":599,"className":1211,"style":1213},"/logo-light.svg",[1212],"dark:hidden","height:4rem;width:auto;flex-shrink:0;",[632,1215],{"src":1216,"alt":599,"className":1217,"style":1213},"/logo-dark.svg",[1218,1219],"hidden","dark:block",[1204,1221,1223,1224,1223,1229,1223,1233,1207],{"style":1222},"display:flex;flex-direction:column;gap:0.375rem;","\n    ",[1225,1226,1228],"span",{"style":1227},"font-size:0.6875rem;font-weight:800;letter-spacing:0.18em;text-transform:uppercase;color:var(--color-amber-500);","GANGSTA AGENTS",[1225,1230,1232],{"style":1231},"font-size:1rem;font-weight:600;color:var(--site-heading-h3h4);line-height:1.3;","Spec-Driven Development Framework",[1225,1234,1236],{"style":1235},"font-size:0.875rem;color:var(--site-fg);opacity:0.55;line-height:1.5;","Organized like a family. Built for humans and AI agents.",[1238,1239,1200],"h1",{"id":1240},"the-family-vs-the-team",[145,1242,1243],{},"Agile gave us teams. Gangsta Agents gives us families.",[145,1245,1246],{},"The difference is not aesthetic. It is not branding. It is a fundamentally different theory of how humans — and now agents — should organize around work that matters.",[202,1248,1250],{"id":1249},"the-team-is-a-convenience","The Team Is a Convenience",[145,1252,1253],{},"An agile team is a temporary arrangement of interchangeable contributors. The methodology is explicit about this: roles are fluid, members are swappable, the backlog is the only thing that persists. When a sprint ends, the team disbands its commitments and starts fresh. When a member leaves, the standup continues without them by Wednesday.",[145,1255,1256,1257,1260],{},"This is by design. Agile optimized for ",[161,1258,1259],{},"throughput under uncertainty",". It assumed the work was unknowable, the requirements would change, and the safest bet was to keep everyone loosely coupled so the system could survive any single defection.",[145,1262,1263],{},"It worked. For a while. For a kind of work.",[145,1265,1266],{},"But loosely coupled people produce loosely coupled outcomes. When nobody owns the whole, nobody bleeds for the whole.",[202,1268,1270],{"id":1269},"the-family-is-a-bond","The Family Is a Bond",[632,1272],{"src":1273,"alt":1274,"style":636},"/family-vs-agile.svg","Agile Team vs Gangsta Agents Family — structure comparison",[145,1276,1277,1278],{},"A family is not a team. It is a structure where every member has sworn — in blood, in code, by the rules — that the family's outcome is their personal outcome. There is no \"I finished my ticket.\" There is only: ",[195,1279,1280],{},"did the job get done, and did the family come out ahead?",[145,1282,1283],{},"This sounds like a metaphor. It is not. It is the operational reality of how Gangsta Agents runs.",[145,1285,1286,1287,1290,1291],{},"When the Underboss decomposes a contract into work packages, those packages are not Jira tickets to be picked up by whoever is available. They are ",[161,1288,1289],{},"assignments to agents who will answer for the outcome",". When a Crew Lead reviews a deliverable from an agent, they are not running a code review checklist. They are asking: ",[195,1292,1293],{},"did this agent honor the contract, or did they embarrass the family?",[145,1295,1296],{},"Every member feels the weight of every decision. That weight is not a burden — it is the source of the discipline.",[202,1298,1300],{"id":1299},"more-strict-than-agile","More Strict Than Agile",[145,1302,1303],{},"Agile is permissive by default. The retrospective is where you discuss what went wrong. The sprint is where you ship anyway.",[145,1305,1306],{},"Gangsta Agents does not work that way. The Contract is signed before any code is written. The Spec is supreme. An agent that deviates from the Contract — even with good intentions, even with a \"better idea\" — has violated the code. The Crew Lead will reject the deliverable. The Underboss will hear about it. The Don decides what happens next.",[145,1308,1309],{},"There are no \"let's just ship it and iterate.\" There is the Contract, Execution, The Delivery. Each phase has a gate. Each gate requires the Don's approval. There is no auto-advance. There is no \"we'll fix it in the next sprint.\"",[632,1311],{"src":634,"alt":635,"style":636},[145,1313,1314],{},"This is stricter than any agile framework you have worked under. And it is stricter on purpose, because the cost of a quiet deviation in an AI-driven workflow is not a missed sprint goal — it is a hallucinated implementation that compounds across every downstream decision.",[202,1316,1318],{"id":1317},"more-adaptive-than-agile","More Adaptive Than Agile",[145,1320,1321,1322],{},"Here is the part that confuses people who only see the strictness: ",[161,1323,1324],{},"Gangsta Agents is more adaptive than agile, not less.",[145,1326,1327],{},"Agile's adaptivity is bureaucratic. You adapt by waiting for the next planning meeting. You adapt by re-pointing stories. You adapt by negotiating scope with a product owner who is three layers removed from the work.",[145,1329,1330],{},"In a family, adaptation happens at the speed of conversation. The Don speaks. The Underboss adjusts the execution plan. The Crew Lead redirects the agents. There is no ceremony to wait for. There is no quarterly roadmap to renegotiate. The Consigliere can call a truth check at any moment and stop a Heist that has gone off course — without anyone's permission, because the Consigliere stands outside the chain of command precisely so they can.",[145,1332,1333,1334,1337,1338,1341],{},"The strictness is in the ",[195,1335,1336],{},"structure",". The adaptivity is in the ",[195,1339,1340],{},"response",". Agile inverted these and got slow rigidity dressed up as flexibility. Gangsta Agents inverts the inversion.",[202,1343,1345],{"id":1344},"why-this-matters-now","Why This Matters Now",[145,1347,1348],{},"When the workforce was entirely human, the difference between a team and a family was a matter of culture and tolerance for intensity. Some people thrive in families. Some people need the safety of teams. Both could ship software.",[145,1350,1351,1352,1355],{},"That symmetry is broken now. AI agents do not need psychological safety. They need ",[161,1353,1354],{},"constraints, ownership, and clear authority",". An agent given a Jira ticket and told to \"just iterate\" will hallucinate its way through six commits before lunch. An agent dispatched as an executor under a Crew Lead, against a signed Contract, with the Ledger watching, will produce work that survives review.",[145,1357,1358],{},"The family structure is not a metaphor for AI orchestration. It is the most accurate organizational pattern we have found for it. Every member — human or agent — feels the weight. Every decision routes through a hierarchy that exists to be respected, not bypassed. Every deviation is named and accounted for.",[202,1360,1362],{"id":1361},"the-bond-is-the-product","The Bond Is the Product",[145,1364,1365],{},"Agile teams produce features. Gangsta Agents families produce outcomes — and the bond is what makes the outcome possible.",[145,1367,1368],{},"When an agent knows the Crew Lead will review the deliverable against the Contract, they write the code differently. When a Crew Lead knows the Underboss will compare the territory's output against the execution plan, they review differently. When the Don knows the Consigliere has standing authority to stop the operation, they decide differently.",[145,1370,1371,1372,1375],{},"This is not a hierarchy of distrust. It is a hierarchy of ",[161,1373,1374],{},"mutual accountability",". Everyone is watching everyone, because everyone has sworn to the same outcome.",[145,1377,1378],{},"That is what a family is. That is what a team can never be.",[145,1380,1381],{},[195,1382,1383],{},"The Gangsta Agents Family does not have teammates. It has family.",{"title":289,"searchDepth":16,"depth":16,"links":1385},[1386,1387,1388,1389,1390,1391],{"id":1249,"depth":16,"text":1250},{"id":1269,"depth":16,"text":1270},{"id":1299,"depth":16,"text":1300},{"id":1317,"depth":16,"text":1318},{"id":1344,"depth":16,"text":1345},{"id":1361,"depth":16,"text":1362},"Why Gangsta Agents replaces the agile team with the family — and why every member carries more weight, more discipline, and more freedom than any sprint board ever allowed.",{"date":1394},"2026-04-18","/blog/2026-04-18-the-family-vs-the-team",{"title":1200,"description":1392},"blog/2026-04-18-the-family-vs-the-team","FG1fnXzsIdiFC-A5SYtRuqkm8HWt65T84BSP-veci1Y",1777641827979]