ring:planning-large-features
Planning the 10-gate Full Track pre-dev workflow (research, PRD, feature map, design validation, TRD, API design, data model, dependency map, phases and epics, task creation, delivery planning) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use ring:planning-small-features). Plans only — no edits.
What this skill does
# Full Track Pre-Dev Workflow (10 Gates)
## When to use
- Feature takes >=2 days to implement
- Adds new external dependencies (APIs, databases, libraries)
- Creates new data models or entities
- Requires multi-service integration
- Uses new architecture patterns
- Requires team collaboration
## Skip when
- Feature is simple (<2 days, existing patterns) - use ring:planning-small-features instead
- No new dependencies, data models, or architecture patterns needed
## Sequence
**Runs before:** ring:writing-plans, ring:running-dev-cycle
## Related
**Complementary:** ring:planning-small-features, ring:writing-plans, ring:creating-worktrees
**Skills orchestrated:**
- ring:researching-features
- ring:writing-prds
- ring:mapping-feature-relationships
- ring:validating-ux-completeness
- ring:writing-trds
- ring:designing-api-contracts
- ring:designing-data-model
- ring:pinning-dependency-versions
- ring:decomposing-phases-and-epics
- ring:detailing-tasks
- ring:planning-delivery
Running the **Full Track** pre-development workflow for features that take ≥2 days, add new external dependencies, create new data models, require multi-service integration, use new architecture patterns, or require team collaboration.
For simple features (<2 days, existing patterns), use `ring:planning-small-features` instead.
## Gate Map
| Gate | Skill | Output | Track |
|------|-------|--------|-------|
| 0 | ring:researching-features | research.md | Full |
| 1 | ring:writing-prds | prd.md | Full |
| 1.5 | ring:validating-ux-completeness | design-validation.md | Full (if UI) |
| 2 | ring:mapping-feature-relationships | feature-map.md | Full |
| 2.5 | ring:validating-ux-completeness | design-validation.md | Full (if UI, Large) |
| 3 | ring:writing-trds | trd.md | Full |
| 4 | ring:designing-api-contracts | api-design.md | Full |
| 5 | ring:designing-data-model | data-model.md | Full |
| 6 | ring:pinning-dependency-versions | dependencies.md | Full |
| 7 | ring:decomposing-phases-and-epics | tasks.md (phased plan: phases + epics) | Full |
| 8 | ring:detailing-tasks | Phase 1 tasks written into tasks.md | Full |
| 9 | ring:planning-delivery | delivery-roadmap.md + .json | Full |
All artifacts saved to: `docs/pre-dev/<feature-name>/`
## Step 1: Gather Feature Name
AskUserQuestion: "What is the name of your feature?" (kebab-case, e.g., "auth-system", "payment-processing")
## Step 2: Topology Discovery (MANDATORY)
Execute topology discovery per [shared-patterns/topology-discovery.md](../shared-patterns/topology-discovery.md). Discovers project structure (fullstack/backend-only/frontend-only), repository organization (single-repo/monorepo/multi-repo), module paths, and UI configuration. Store as `TopologyConfig` for all subsequent gates.
## Step 3: Gather Feature-Specific Inputs
**Q2 (CONDITIONAL):** Auth requirements — auto-detect from `go.mod` (`lib-auth` present → skip). Options: None, User only, User + permissions, Service-to-service, Full.
**Q3 (CONDITIONAL):** License requirements — auto-detect from `go.mod` (`lib-license-go` present → skip). Options: No, Yes.
**Q4 (MANDATORY):** Has UI? Options: Yes, No. Always ask — do not assume from feature description.
**Q5 (if Q4=Yes):** UI component library — auto-detect from package.json. Options: shadcn/ui + Radix (recommended), Chakra UI, Headless UI, Material UI, Ant Design, Custom.
**Q6 (if Q4=Yes):** Styling approach — auto-detect from package.json. Options: TailwindCSS (recommended), CSS Modules, Styled Components, Sass/SCSS, Vanilla CSS.
## Step 4: Execute Gates Sequentially
Each gate invokes its sub-skill. Human approval required at each gate before proceeding.
**Gate execution rules:**
- Gate 1.5 / 2.5 (Design Validation): only if Q4=Yes
- Gate 2 (Feature Map): always for Full Track
- Gates 4-6 (API Design, Data Model, Dependency Map): always for Full Track
- Gate 8 (Task Creation): always for Full Track
## Gate Progress Tracking
Save state to `docs/pre-dev/{feature}/workflow-state.json`:
```json
{
"track": "full",
"feature": "{feature-name}",
"currentGate": 0,
"gates": {
"0": "PENDING", "1": "PENDING", "1.5": "SKIP|PENDING",
"2": "PENDING", "2.5": "SKIP|PENDING", "3": "PENDING",
"4": "PENDING", "5": "PENDING", "6": "PENDING",
"7": "PENDING", "8": "PENDING", "9": "PENDING"
},
"topology": {},
"inputs": {"hasUI": false, "authRequired": false, "licenseRequired": false, "uiLibrary": null, "styling": null}
}
```
## Execution Mode
AskUserQuestion at start: "Execution mode?"
- **Automatic** — all gates execute, pause only on failure
- **Manual** — checkpoint and wait for approval after each gate
## Completion
After Gate 9 approved: artifacts are the execution baseline. Use `ring:running-dev-cycle` to execute.
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.