Loading...
Loading...
Found 23 Skills
Use after research (Z01 files exist) to create implementation plan - follow structured workflow
Sequence tasks from a feature breakdown into an optimal execution order, identify dependencies and parallelization opportunities, and create an agent-ready execution sequence. Use when you have a feature breakdown and need to determine the correct order to build tasks and which can run in parallel.
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Creates implementation-ready plans and specs for complex changes without writing code. Use when the user asks for a plan/spec/roadmap, requests a detailed plan, or when a change spans multiple files/systems and needs discovery, sequencing, or architecture decisions.
Discussion entry when ideas are still vague — first conduct triage through 1-2 rounds of dialogue to determine which downstream process this discussion should eventually go to: if the idea is clear enough, proceed directly to feature-design; if the direction of a small requirement is set, continue the discussion within the feature and document it in `{slug}-brainstorm.md`; if a large requirement cannot fit into a single feature, hand it over to roadmap for decomposition. The role of AI is a thinking partner, not a recorder — dig out the real problem the user wants to solve, proactively evaluate when the user brings a solution, and propose alternative directions when necessary. Trigger scenarios: when the user says "I have an idea that's not clear yet", "Let's brainstorm first", "I want to do something but it's still vague", "Let's talk about this area", "The function direction is still undecided", or when the user comes with a specific solution but wants to hear other ideas first. Bugs (go to issue) and refactoring (go to refactor) are not handled here.
Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management.
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Plan and file goals and feature issues through conversation. Use when the user wants to create goals, plan features, file issues, or discuss what to build next.
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive".
This skill should be used when a user wants to decompose an Epic into its complete set of Features all at once, invoked automatically after write-epic completes, or triggered by phrases like "create all features for this epic", "walk me through all the features", "let's break down this epic", or "plan the features for epic
Use when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.