setup
Initialize the design doc backlog system in a project. Use when the user wants to: - Set up design docs for a project - Initialize the backlog system - Configure design doc workflow - Add design doc task management
What this skill does
# Setup Design Doc Backlog System This skill helps users set up the design doc driven task management system in their project. ## When to Use Activate when the user says things like: - "set up design docs" - "initialize the backlog" - "configure design doc workflow" - "add task management with design docs" ## Setup Process ### 1. Gather Information Ask the user for: - **Project prefix**: A short uppercase identifier (e.g., `ACME`, `GF`, `DAB`) used in task IDs like `[ACME-001-01]` Check if they already have: - A `README.org` with `#+PROJECT_PREFIX:` set (use that) - Existing `docs/design/` directory (don't overwrite) - Existing `backlog.org` (don't overwrite) ### 2. Create Directory Structure Create these directories if they don't exist: ``` docs/design/ ``` ### 3. Create Files from Templates The templates are in the plugin's `templates/` directory. Copy them with PROJECT substitution: | Template | Destination | Substitution | |----------|-------------|--------------| | `readme-project.org` | `README.org` | Replace `PROJECT` with prefix | | `readme-design.org` | `docs/design/README.org` | None | | `org-setup.org` | `org-setup.org` | Replace `PROJECT` with prefix | | `backlog-template.org` | `backlog.org` | Replace `PROJECT` with prefix | | `design-doc-template.org` | `docs/design/000-template.org` | Replace `PROJECT` with prefix | | `changelog-template.md` | `CHANGELOG.md` | None | **Important**: Check if files exist before writing. Ask the user before overwriting. ### 4. Update CLAUDE.md Append or merge the following into the project's CLAUDE.md (create if needed): ```markdown ## Design Doc Workflow This project uses design docs for task management. Design docs live in `docs/design/`. ### Key Files - `backlog.org` - Working surface for active tasks - `docs/design/*.org` - Design documents (source of truth) - `README.org` - Project config (prefix, categories, statuses) ### Workflow 1. Create design docs with `/backlog:new-design-doc` 2. Queue tasks with `/backlog:task-queue <id>` 3. Start work with `/backlog:task-start <id>` 4. Complete with `/backlog:task-complete <id>` ### Task ID Format `[PREFIX-NNN-XX]` where: - PREFIX = project prefix (e.g., ACME) - NNN = design doc number - XX = task sequence ``` ### 5. Explain What Was Created After setup, explain: - What files were created and their purpose - How to create a first design doc - Available commands (`/backlog:new-design-doc`, etc.) ## Example Interaction ``` User: Set up design docs for this project Claude: I'll help you set up the design doc backlog system. What project prefix would you like to use? This is a short uppercase identifier (like ACME, GF, or DAB) that will appear in task IDs like [ACME-001-01]. User: ACME Claude: Great! Let me set up the backlog system with prefix ACME. [Creates files...] Done! I've created: - README.org - Project config with categories and statuses - org-setup.org - Shared org-mode configuration - backlog.org - Your working surface for active tasks - docs/design/README.org - Index of design documents - docs/design/000-template.org - Template for new design docs - CHANGELOG.md - For tracking releases To create your first design doc, use: /backlog:new-design-doc "Your Feature Title" This will create a numbered design doc with tasks you can then queue to your backlog. ``` ## Template Content When writing files, read the template content from the plugin's templates directory and perform the PROJECT → prefix substitution.
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.