II.
Page JSON
Structured · livepage:docs-reference-process-selection
Babysitter Process Selection Guide json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-reference-process-selection",
"_kind": "Page",
"_file": "wiki/docs/reference/process-selection.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/reference/PROCESS_SELECTION.md",
"sourceKind": "repo-docs",
"title": "Babysitter Process Selection Guide",
"displayName": "Babysitter Process Selection Guide",
"slug": "docs/reference/process-selection",
"articlePath": "wiki/docs/reference/PROCESS_SELECTION.md",
"article": "\n# Babysitter Process Selection Guide\n\nA comprehensive guide to help you choose the right process/methodology for your project needs.\n\n---\n\n## Quick Decision Tree\n\nUse this text-based flowchart to quickly identify the best methodology for your needs:\n\n```\n START HERE\n |\n v\n +-------------------------+\n | Do you have existing |\n | codebase to work with? |\n +-------------------------+\n | |\n YES NO\n | |\n v v\n +---------------+ +----------------+\n | Brownfield | | Greenfield |\n | Project | | (New Project) |\n +---------------+ +----------------+\n | |\n v v\n +------------------+ +--------------------+\n | Need governance/ | | What's your main |\n | compliance? | | priority? |\n +------------------+ +--------------------+\n | | |\n YES NO +-----+-----+-----+\n | | | | | |\n v v v v v v\n +--------+ +--------+ Speed Quality Gov Team\n |Spec-Kit| | GSD | | | | |\n |Brown- | |Codebase| v v v v\n |field | |Mapping | Ralph/ TDD Spec- Scrum/\n +--------+ +--------+ Devin QC Kit Agile\n Kanban\n\n Legend:\n - Spec-Kit Brownfield: Governance + existing code\n - GSD Codebase Mapping: Systematic brownfield analysis\n - Ralph/Devin: Quick iterations, autonomous coding\n - TDD QC: Test-driven development with quality gates\n - Spec-Kit: Full governance, enterprise requirements\n - Scrum/Agile/Kanban: Team coordination, sprints, flow\n```\n\n---\n\n## Quick Reference Table\n\n| Methodology | Best For | Complexity | Human Gates | Key Artifacts |\n|-------------|----------|------------|-------------|---------------|\n| **GSD** | Complete products, systematic development | Medium | Vision, Plans, UAT | PROJECT.md, ROADMAP.md |\n| **Spec-Kit** | Enterprise, governance-heavy projects | High | Every phase | Constitution, Spec, Plan, Tasks |\n| **TDD Quality Convergence** | Technical features, test-first | Medium | Plan, Iterations, Final | Tests, Implementation |\n| **Devin** | Full features, autonomous coding | Medium | Plan, Debug, Deploy | Plan, Code, Tests |\n| **Ralph** | Quick iterations, persistent tasks | Low | Optional per iteration | Iteration results |\n| **Agile/Scrum** | Sprint-based teams, stakeholder collaboration | Medium-High | Sprint ceremonies | Backlog, Burndown, Retros |\n| **Kanban** | Continuous delivery, flow optimization | Low-Medium | Replenishment | Board, CFD, Metrics |\n| **BDD** | Stakeholder collaboration, living documentation | Medium | Discovery, Review | Gherkin specs, Tests |\n| **DDD** | Complex domains, microservices | High | Phase reviews | Context maps, Aggregates |\n| **Example Mapping** | Feature discovery, requirement clarity | Low | Workshop | Rules, Examples, Questions |\n| **ATDD/TDD** | Technical correctness, refactoring | Medium | Test design | Acceptance tests, Unit tests |\n\n---\n\n## Use Case Examples\n\n### \"I want to build a new project from scratch\"\n**Recommended: GSD (Get Shit Done)**\n\nGSD provides systematic project development with:\n- Vision capture and research\n- Phased milestone planning\n- Parallel task execution\n- UAT and verification loops\n\n```bash\nbabysitter run:create \\\n --process-id gsd/new-project \\\n --entry library/methodologies/gsd/new-project.js#process \\\n --inputs '{\"projectName\": \"My New App\"}'\n```\n\n**Also consider:** Spec-Kit if you need formal governance, or Devin for autonomous feature development.\n\n---\n\n### \"I want test-driven development with quality gates\"\n**Recommended: TDD Quality Convergence**\n\nTDD Quality Convergence provides:\n- Agent-based planning with TDD principles\n- Red-Green-Refactor cycle\n- Iterative quality scoring (0-100)\n- Parallel quality checks (coverage, lint, types, security)\n- Convergence until target quality reached\n\n```bash\nbabysitter run:create \\\n --process-id babysitter/tdd-quality-convergence \\\n --entry library/tdd-quality-convergence.js#process \\\n --inputs '{\"feature\": \"User Authentication\", \"targetQuality\": 90}'\n```\n\n**Also consider:** ATDD/TDD for simpler test-first workflows, or BDD for stakeholder collaboration.\n\n---\n\n### \"I have governance requirements and need formal specifications\"\n**Recommended: Spec-Kit**\n\nSpec-Kit provides:\n- Constitution with governance principles\n- Executable specifications\n- Quality checklists (\"unit tests for English\")\n- Full audit trail\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/spec-driven-development \\\n --entry library/methodologies/spec-driven-development.js#process \\\n --inputs '{\"projectName\": \"Enterprise System\", \"developmentPhase\": \"greenfield\"}'\n```\n\n**Variants:**\n- `spec-kit-constitution.js` - Governance principles only\n- `spec-kit-quality-checklist.js` - Quality validation\n- `spec-kit-brownfield.js` - Adding to existing systems\n\n---\n\n### \"I want quick iterations with minimal ceremony\"\n**Recommended: Ralph or Devin**\n\n**Ralph** - Simple persistent loop:\n- Execute task until DONE signal\n- Minimal overhead\n- Good for autonomous completion\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/ralph \\\n --entry library/methodologies/ralph.js#process \\\n --inputs '{\"task\": \"Implement login feature\", \"maxIterations\": 10}'\n```\n\n**Devin** - Plan-Code-Debug-Deploy:\n- More structured than Ralph\n- Includes quality scoring\n- Deployment phase\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/devin \\\n --entry library/methodologies/devin.js#process \\\n --inputs '{\"feature\": \"Shopping Cart\", \"targetQuality\": 85}'\n```\n\n---\n\n### \"I need to coordinate a team with sprints\"\n**Recommended: Scrum or Agile**\n\nScrum/Agile provides:\n- Product backlog management\n- Sprint planning and execution\n- Daily scrums, reviews, retrospectives\n- Velocity tracking\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/scrum \\\n --entry library/methodologies/scrum/scrum.js#process \\\n --inputs '{\"projectName\": \"Team Project\", \"sprintDuration\": 2, \"sprintCount\": 6}'\n```\n\n**Also consider:** Kanban for continuous flow without fixed sprints.\n\n---\n\n### \"I want continuous delivery without fixed iterations\"\n**Recommended: Kanban**\n\nKanban provides:\n- Visual workflow management\n- WIP limits and flow optimization\n- Service classes for prioritization\n- Continuous improvement\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/kanban \\\n --entry library/methodologies/kanban/kanban.js#process \\\n --inputs '{\"projectName\": \"DevOps Pipeline\", \"cycles\": 10}'\n```\n\n---\n\n### \"I want stakeholders involved in defining behavior\"\n**Recommended: BDD (Specification by Example)**\n\nBDD provides:\n- Discovery workshops with stakeholders\n- Given-When-Then scenarios\n- Living documentation\n- Executable specifications\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/bdd-specification-by-example \\\n --entry library/methodologies/bdd-specification-by-example/bdd-process.js#process \\\n --inputs '{\"projectName\": \"E-commerce\", \"feature\": \"Checkout process\"}'\n```\n\n---\n\n### \"I'm building a complex domain with microservices\"\n**Recommended: Domain-Driven Design (DDD)**\n\nDDD provides:\n- Strategic design (subdomains, bounded contexts)\n- Tactical design (entities, aggregates, services)\n- Ubiquitous language\n- Context mapping\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/domain-driven-design \\\n --entry library/methodologies/domain-driven-design/domain-driven-design.js#process \\\n --inputs '{\"projectName\": \"E-Commerce Platform\", \"complexity\": \"complex\"}'\n```\n\n---\n\n### \"I need to add features to an existing codebase\"\n**Recommended: Spec-Kit Brownfield or GSD Codebase Mapping**\n\n**Spec-Kit Brownfield:**\n- Analyzes existing patterns\n- Infers or validates constitution\n- Plans integration carefully\n\n```bash\nbabysitter run:create \\\n --process-id methodologies/spec-kit-brownfield \\\n --entry library/methodologies/spec-kit-brownfield.js#process \\\n --inputs '{\"featureName\": \"2FA\", \"existingCodebase\": \"./src\"}'\n```\n\n**GSD Codebase Mapping:**\n- Architecture understanding\n- Pattern identification\n- Integration planning\n\n```bash\nbabysitter run:create \\\n --process-id gsd/map-codebase \\\n --entry library/methodologies/gsd/map-codebase.js#process \\\n --inputs '{\"projectPath\": \"./src\"}'\n```\n\n---\n\n## Methodology Descriptions\n\n### Core Methodologies\n\n#### GSD (Get Shit Done)\nSystematic project development preventing context degradation through:\n- **Discuss Phase**: Capture implementation preferences\n- **Plan Phase**: Research-informed task planning with verification\n- **Execute Phase**: Parallel task execution with atomic commits\n- **Verify Phase**: UAT and automated diagnosis\n\n**Documentation:** [gsd/README.md](../../library/methodologies/gsd/README.md)\n\n---\n\n#### Spec-Kit (Spec-Driven Development)\nExecutable specifications that drive implementation:\n- **Constitution**: Governance principles and standards\n- **Specification**: User stories with acceptance criteria\n- **Plan**: Technical architecture and stack\n- **Tasks**: Ordered, actionable implementation tasks\n- **Quality Checklists**: \"Unit tests for English\"\n\n**Documentation:** [SPEC-KIT.md](../../library/methodologies/spec-kit/README.md)\n\n---\n\n#### TDD Quality Convergence\nTest-driven development with iterative quality improvement:\n- Agent-based planning with TDD principles\n- Quality scoring across multiple dimensions\n- Convergence loop until target quality reached\n- Parallel quality checks\n\n**Documentation:** [tdd-quality-convergence.md](../../library/tdd-quality-convergence.md)\n\n---\n\n#### Devin Style\nAutonomous software engineering workflow:\n- **Plan**: Architecture and implementation strategy\n- **Code**: Feature implementation\n- **Debug**: Iterative test-fix cycles\n- **Deploy**: Production deployment\n\n---\n\n#### Ralph Loop\nSimple, persistent iteration loop:\n- Execute task repeatedly until DONE signal\n- Minimal ceremony and overhead\n- Good for autonomous task completion\n\n---\n\n### Agile Methodologies\n\n#### Scrum\nIterative framework with defined roles and ceremonies:\n- Sprint-based timeboxed iterations\n- Product Owner, Scrum Master, Development Team\n- Sprint Planning, Daily Scrum, Review, Retrospective\n- Velocity tracking and burndown charts\n\n---\n\n#### Kanban\nContinuous flow management:\n- Visual workflow with WIP limits\n- Pull-based system\n- Service classes (Expedite, Standard, Fixed Date, Intangible)\n- Cycle time and throughput metrics\n\n---\n\n#### Agile (General)\nSprint-based iterative development with:\n- Product backlog management\n- Sprint cycles with planning and review\n- Continuous improvement through retrospectives\n\n---\n\n### Specification & Design Methodologies\n\n#### BDD (Specification by Example)\nCollaborative approach capturing requirements as concrete examples:\n- Discovery workshops with stakeholders\n- Gherkin scenarios (Given-When-Then)\n- Living documentation\n- Executable specifications\n\n**Documentation:** [bdd-specification-by-example/README.md](../../library/methodologies/bdd-specification-by-example/README.md)\n\n---\n\n#### Domain-Driven Design (DDD)\nStrategic and tactical design for complex domains:\n- Subdomain classification (Core, Supporting, Generic)\n- Bounded contexts and context mapping\n- Entities, Value Objects, Aggregates\n- Domain events and services\n\n**Documentation:** [domain-driven-design/README.md](../../library/methodologies/domain-driven-design/README.md)\n\n---\n\n#### Example Mapping\nCollaborative requirement discovery:\n- Stories, Rules, Examples, Questions\n- Workshop-based discovery\n- Foundation for BDD scenarios\n\n**Documentation:** [example-mapping/README.md](../../library/methodologies/example-mapping/README.md)\n\n---\n\n### Other Methodologies\n\n| Methodology | Description |\n|-------------|-------------|\n| **ATDD/TDD** | Acceptance test-driven development with unit test cycles |\n| **Feature-Driven Development** | Feature-centric development with two-week cycles |\n| **Hypothesis-Driven Development** | Experiment-based validation of product assumptions |\n| **Jobs To Be Done** | Customer-centric feature prioritization |\n| **Impact Mapping** | Goal-oriented delivery planning |\n| **Shape Up** | 6-week appetite-based development cycles |\n| **Extreme Programming (XP)** | Technical excellence through pair programming, CI, etc. |\n\n---\n\n## Comparison Matrix\n\n### By Project Phase\n\n| Phase | Best Methodologies |\n|-------|-------------------|\n| **Discovery/Research** | Example Mapping, BDD Discovery, GSD Discuss |\n| **Architecture** | DDD, Spec-Kit Constitution, GSD New Project |\n| **Planning** | Scrum Sprint Planning, Spec-Kit, GSD Plan Phase |\n| **Implementation** | TDD QC, Devin, Ralph, Kanban |\n| **Testing** | BDD, ATDD/TDD, TDD Quality Convergence |\n| **Deployment** | Devin, Kanban, Scrum Release |\n\n### By Team Size\n\n| Team Size | Recommended |\n|-----------|-------------|\n| **Solo developer** | Ralph, Devin, GSD |\n| **Small team (2-5)** | Kanban, GSD, Spec-Kit |\n| **Medium team (5-9)** | Scrum, Agile, BDD |\n| **Large team (10+)** | Scrum, DDD (bounded contexts), Spec-Kit |\n\n### By Certainty Level\n\n| Requirements Certainty | Recommended |\n|------------------------|-------------|\n| **High certainty** | TDD QC, Spec-Kit, Devin |\n| **Medium certainty** | Scrum, GSD, BDD |\n| **Low certainty** | Kanban, Ralph, Hypothesis-Driven |\n| **Unknown** | Example Mapping, BDD Discovery, GSD Discuss |\n\n### By Quality Focus\n\n| Quality Priority | Recommended |\n|------------------|-------------|\n| **Maximum quality** | TDD Quality Convergence, Spec-Kit |\n| **Balanced** | GSD, Scrum, BDD |\n| **Speed over quality** | Ralph, Devin |\n| **Compliance required** | Spec-Kit, BDD (living docs) |\n\n---\n\n## Domain-Specific Process Selector\n\nChoose based on your domain specialization:\n\n### Software Development\n\n| Domain | Recommended Process | Reason |\n|--------|-------------------|--------|\n| **Web Development** | GSD, Devin, BDD | Rapid iteration, stakeholder demos |\n| **Mobile Development** | Scrum, BDD | Sprint-based, platform testing |\n| **Desktop Development** | GSD, TDD QC | Quality focus, fewer deployments |\n| **Game Development** | Kanban, GSD | Continuous flow, creative iteration |\n| **Embedded Systems** | Spec-Kit, TDD QC | Safety-critical, formal specs |\n\n### Data & AI\n\n| Domain | Recommended Process | Reason |\n|--------|-------------------|--------|\n| **Data Engineering** | Kanban, GSD | Pipeline management, continuous flow |\n| **Data Science/ML** | Hypothesis-Driven, GSD | Experimental, iterative |\n| **AI Agents** | TDD QC, BDD | Behavior validation, quality gates |\n\n### Operations & Infrastructure\n\n| Domain | Recommended Process | Reason |\n|--------|-------------------|--------|\n| **DevOps/SRE** | Kanban | Continuous flow, incident response |\n| **Security/Compliance** | Spec-Kit | Governance, audit trails |\n| **Platform Engineering** | DDD, Spec-Kit | Complex domains, service boundaries |\n\n### Product & Design\n\n| Domain | Recommended Process | Reason |\n|--------|-------------------|--------|\n| **Product Management** | Impact Mapping, JTBD | Goal-oriented, customer-centric |\n| **UX/UI Design** | BDD, Example Mapping | Stakeholder collaboration |\n| **Technical Documentation** | GSD, Spec-Kit | Systematic, quality gates |\n\n### Scientific & Engineering\n\n| Domain | Recommended Process | Reason |\n|--------|-------------------|--------|\n| **Scientific Discovery** | Hypothesis-Driven | Experimental validation |\n| **Engineering (Aerospace, Automotive, etc.)** | Spec-Kit, TDD QC | Safety-critical, compliance |\n| **Algorithms/Optimization** | TDD QC | Correctness verification |\n\n---\n\n## Combining Methodologies\n\nMany projects benefit from combining approaches:\n\n### Spec-Kit + TDD\n```javascript\n// 1. Use Spec-Kit for requirements and planning\nconst spec = await runProcess('methodologies/spec-driven-development', { ... });\n\n// 2. Use TDD QC for implementation\nfor (const task of spec.tasks) {\n await runProcess('babysitter/tdd-quality-convergence', {\n feature: task.title,\n targetQuality: 85\n });\n}\n```\n\n### DDD + BDD\n```javascript\n// 1. Use DDD for strategic design\nconst design = await runProcess('methodologies/domain-driven-design', { ... });\n\n// 2. Use BDD for each bounded context\nfor (const context of design.boundedContexts) {\n await runProcess('methodologies/bdd-specification-by-example', {\n feature: context.name\n });\n}\n```\n\n### GSD + Kanban\n```javascript\n// 1. Use GSD for project initialization\nconst project = await runProcess('gsd/new-project', { ... });\n\n// 2. Use Kanban for ongoing delivery\nawait runProcess('methodologies/kanban', {\n initialBacklog: project.roadmap.tasks\n});\n```\n\n---\n\n## Documentation Links\n\n### Core Documentation\n- [Process Library README](../../library/README.md) - Built-in library overview\n- [GSD README](../../library/methodologies/gsd/README.md) - Get Shit Done workflows\n- [GSD Quick Start](../../library/methodologies/gsd/QUICK_START.md) - GSD quick reference\n- [Spec-Kit](../../library/methodologies/spec-kit/README.md) - Spec-driven development\n- [TDD Quality Convergence](../../library/tdd-quality-convergence.md) - Test-driven with quality gates\n\n### Methodology Documentation\n- [BDD/Specification by Example](../../library/methodologies/bdd-specification-by-example/README.md)\n- [Domain-Driven Design](../../library/methodologies/domain-driven-design/README.md)\n- [Example Mapping](../../library/methodologies/example-mapping/README.md)\n- [Kanban](../../library/methodologies/kanban/README.md)\n- [Feature-Driven Development](../../library/methodologies/feature-driven-development/README.md)\n- [Hypothesis-Driven Development](../../library/methodologies/hypothesis-driven-development/README.md)\n- [ATDD/TDD](../../library/methodologies/atdd-tdd/README.md)\n- [Jobs To Be Done](../../library/methodologies/jobs-to-be-done/README.md)\n\n### Domain Specializations\n- [Technical Documentation](../../library/specializations/technical-documentation/README.md)\n- [Data Science/ML](../../library/specializations/data-science-ml/README.md)\n- [DevOps/SRE](../../library/specializations/devops-sre-platform/README.md)\n- [Security/Compliance](../../library/specializations/security-compliance/README.md)\n- [QA/Testing](../../library/specializations/qa-testing-automation/README.md)\n- [Software Architecture](../../library/specializations/software-architecture/README.md)\n\n---\n\n## Getting Started\n\n1. **Identify your project type** using the decision tree above\n2. **Review the quick reference table** to understand methodology trade-offs\n3. **Read the detailed documentation** for your chosen methodology\n4. **Start with examples** in the `examples/` directories\n5. **Iterate and combine** methodologies as your project evolves\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-02-03\n**Plugin:** babysitter\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": []
}