sdlc:plan
Refine requirements on a Linear ticket through Socratic dialogue. Use this when the user wants to think through a problem, clarify requirements, or evaluate options before starting design work.
What this skill does
# Plan Refining requirements for $ARGUMENTS through Socratic dialogue. In all bash steps below, substitute placeholder names (like ISSUE_ID) with the actual values you stored earlier. ## Workflow 1. **Fetch issue details** from Linear 2. **Understand current state** of the ticket 3. **Engage in Socratic dialogue** to surface requirements and evaluate options 4. **Iteratively update the ticket** as clarity emerges 5. **Confirm readiness** for the design phase ## Step 1: Fetch Issue Details Extract the Linear issue ID from the argument: ```bash ../../scripts/get-linear-issue-id.sh "$ARGUMENTS" ``` Store the output as ISSUE_ID. Fetch the full issue: ```bash linear issue view ISSUE_ID ``` If the fetch fails, inform the user that the plan skill requires a valid Linear issue ID and stop. ## Step 2: Understand Current State Display the issue title and description to the user. Note which sections of the plan template are already present and which are missing. **Plan template sections:** - **Overview** — One to three sentences. What are we doing and why. - **Requirements** — Bulleted list of what must be true when this work is done. - **Options** — For each viable approach: name, one-sentence description, trade-offs. - **Recommendation** — Which option and why. Omit if only one viable option. - **Open Questions** — Anything unresolved that needs answers before or during design. ## Step 3: Socratic Dialogue Begin asking questions to fill in the gaps. Your role is to be a curious, probing thought partner. **Guiding principles:** - Ask one question at a time. Give the user space to think. - Start with "why" before "what" or "how." Understand the problem before exploring solutions. - Challenge assumptions gently. "What happens if we don't do this?" is a valid question. - Surface edge cases. "What about when X?" helps catch gaps early. - When multiple approaches exist, name them and ask the user to weigh trade-offs. - Read codebase files when needed to ground the conversation in reality. Use Read, Grep, and Glob to explore relevant code. - Do not discuss implementation details. Stay at the requirements and options level. **When to move on from a section:** - Overview: move on when you can articulate the "why" in one to three sentences - Requirements: move on when the user agrees the list is complete and testable - Options: move on when trade-offs are clear and the user has a preference - Recommendation: move on when the choice is made and the reasoning is captured - Open Questions: move on when questions are either answered or explicitly deferred to design ## Step 4: Update the Ticket As each section crystallizes through dialogue, update the Linear ticket body to reflect the current state. Build the description incrementally using the plan template structure. ```bash linear issue update ISSUE_ID -d "UPDATED_DESCRIPTION" ``` Do not wait until the end to update. Update after each meaningful exchange so the ticket stays current. The user should be able to read the ticket at any point and see an accurate picture of where planning stands. ## Step 5: Confirm Readiness When all sections are filled in and open questions are resolved (or explicitly deferred), summarize the final state of the ticket to the user. Use AskUserQuestion to confirm: - **Ready for design** — The ticket is in good shape. Proceed to `/sdlc:design ISSUE_ID`. - **Keep refining** — There are still gaps to address. Continue the dialogue. ## Output When the user confirms readiness: ``` Planning complete for ISSUE_ID. Ticket updated with overview, requirements, options, and recommendation. Next step: /sdlc:design ISSUE_ID ```
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.