add-spec
Create a project spec from an idea using the full brainstorming design workflow, then output a no-frills spec for Ralph loops and add-project. Use when the user says "spec a project", "create a spec", "spec this idea", "plan a project", "write a spec", or when add-project delegates Phase 1 spec generation. Runs brainstorming first (clarify → approaches → design approval → design doc), then writes docs/specs/{name}.md with mission, features, flows, screens, and skills mapping.
What this skill does
# Add Spec — Brainstorming to No-Frills Spec
Creates a project specification by running the **full brainstorming workflow** first, then writing a **concise, digestible spec** to `docs/specs/{project-name}.md` for use with add-project and Ralph loops.
## Quick Start
```
1. Run full brainstorming workflow (explore context → clarify → approaches → design sections → approval)
2. Write design doc to docs/plans/YYYY-MM-DD-<topic>-design.md
3. Write no-frills spec to docs/specs/{project-name}.md from the approved design
4. Do NOT invoke writing-plans; add-spec stops at the spec file
```
## Phase 1: Run Brainstorming (Full Workflow)
Follow the **brainstorming** skill end-to-end up to and including the design doc:
1. **Explore project context** — check files, docs, recent commits
2. **Ask clarifying questions** — one at a time; purpose, constraints, success criteria
3. **Propose 2–3 approaches** — with trade-offs and your recommendation
4. **Present design** — in sections scaled to complexity; get user approval after each section
5. **Write design doc** — save to `docs/plans/YYYY-MM-DD-<topic>-design.md`
**Do not** invoke writing-plans or any implementation skill. add-spec terminates after writing the spec file.
## Phase 2: Write No-Frills Spec
After the design doc is written and approved, derive and write the spec to `docs/specs/{project-name}.md`.
Keep the spec **no-frills and easily digestible** for Ralph loops and add-project: short bullets, clear headings, no filler.
### Required Spec Sections
Use this structure. Each section should be concise (bullets or short paragraphs).
```markdown
# {Project Name} — Spec
**Created**: {date}
**Status**: APPROVED
## Mission
- One sentence: what this project is and for whom.
## Main Features
- Feature 1
- Feature 2
- …
## Major User Flows
- Flow 1: step → step → outcome
- Flow 2: …
## Required Screens
- Screen/page name — purpose
- …
## Required Features (from /skills)
Map each requirement to existing skills from the catalog. List skill names and what they cover.
| Requirement | Skill(s) | Notes |
|-------------|----------|-------|
| Auth | auth, auth-dev | better-auth |
| Chat | ai-chat, ai-core | streaming |
| … | … | … |
## Open Gaps
- Anything that has no existing skill; custom implementation needed.
## Constraints / Assumptions
- Hard constraints (APIs, no Docker, auth provider, etc.)
- Assumptions (e.g. local dev only, specific stack).
```
### Rules for the Spec
- **No frills**: no long prose, no duplicate content from the design doc. The spec is a compact reference.
- **Digestible**: someone running add-project or a Ralph loop should grasp scope and skills in one read.
- **Skills mapping**: scan the skill catalog (e.g. from add-feature or skills/*/SKILL.md) to map requirements to skill names; flag gaps as Open Gaps.
## What Gets Created
- `docs/plans/YYYY-MM-DD-<topic>-design.md` — full design (from brainstorming)
- `docs/specs/{project-name}.md` — no-frills spec for add-project / Ralph
## When Invoked by add-project
If add-project delegated Phase 1 to add-spec:
1. Run add-spec as above (brainstorming → design doc → spec file).
2. After the spec is written, return the spec path `docs/specs/{project-name}.md` to add-project so it can proceed to Phase 2 (shell) and Phase 3 (Ralph loop).
## Acceptance Criteria
- [ ] Full brainstorming workflow completed (context, questions, approaches, design approval)
- [ ] Design doc written to docs/plans/YYYY-MM-DD-<topic>-design.md
- [ ] No-frills spec written to docs/specs/{project-name}.md
- [ ] Spec includes all required sections: Mission, Main Features, Major User Flows, Required Screens, Required Features (skills mapping), Open Gaps, Constraints/Assumptions
- [ ] Spec is concise and digestible; no writing-plans or implementation skill invoked
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.