Babysitter planning-design

Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints.

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/spec-kit/skills/planning-design" ~/.claude/skills/a5c-ai-babysitter-planning-design && rm -rf "$T"

manifest: library/methodologies/spec-kit/skills/planning-design/SKILL.md

Planning Design

Overview

Convert a specification into a concrete technical plan with architecture decisions, technology selections, implementation strategy, and risk assessment. All decisions must trace back to specification requirements and comply with constitution constraints.

When to Use

After specification is approved, before task decomposition
When evaluating technology stack options for a feature
When designing system architecture for new components
When assessing implementation risks and defining mitigations

Key Principle

Architecture decisions must be traceable to specification requirements. Technology choices must comply with constitution constraints. Trade-offs must be documented for every significant decision.

Process

Assess technology stack - Evaluate options against constitution requirements
Design architecture - Components, interfaces, data model, integration points
Define strategy - Phases, milestones, testing strategy, deployment approach
Assess risks - Identify risks and define mitigations
Human review - Approve architecture and strategy before task breakdown

Tool Use

Invoke via babysitter process:

methodologies/spec-kit/spec-kit-planning

Full pipeline:

methodologies/spec-kit/spec-kit-orchestrator