planning-design

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

509 stars

bya5c-ai

View on GitHub Installation ↓

Best use case

planning-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using planning-design should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/planning-design/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/spec-kit/skills/planning-design/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/planning-design/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How planning-design Compares

Feature / Agent	planning-design	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

1. **Assess technology stack** - Evaluate options against constitution requirements
2. **Design architecture** - Components, interfaces, data model, integration points
3. **Define strategy** - Phases, milestones, testing strategy, deployment approach
4. **Assess risks** - Identify risks and define mitigations
5. **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`

Related Skills

rest-api-design

509

from a5c-ai/babysitter

RESTful API design principles, versioning, pagination, HATEOAS, and documentation.

design-tokens

509

from a5c-ai/babysitter

Design token management, generation, and multi-platform support.

design-token-transformer

509

from a5c-ai/babysitter

Transform design tokens across multiple formats and platforms. Parse W3C design token format, transform to CSS/SCSS/JS/iOS/Android, handle token aliases and references, and generate documentation.