with one click
design
Research-driven feature design with implementation plan. Combines brainstorming and planning into one flow. Use when designing a new feature. Triggers on "design", "brainstorm", "plan a feature", "how should we build X".
Menu
Research-driven feature design with implementation plan. Combines brainstorming and planning into one flow. Use when designing a new feature. Triggers on "design", "brainstorm", "plan a feature", "how should we build X".
Research-driven brainstorming for feature design. Use when designing a new feature, exploring approaches, or making design decisions. Automatically researches competitors before asking design questions. Triggers on "brainstorm", "design a feature", "how should we build X", or any request to explore approaches for a feature.
Execute implementation plans task by task with verification. Use after /plan to implement the feature. Follows each task exactly, runs verifications, commits frequently. Triggers on "execute the plan", "implement the plan", "run the plan", or after /plan approval.
End-to-end feature development orchestrator. Composes /research, /brainstorm, /plan, and /execute into a single workflow. Use when building a new feature from scratch. Triggers on "build a feature", "implement X from scratch", "full feature development for Y".
Create detailed implementation plans from design specs. Use after brainstorming to create step-by-step implementation plans. Each task is 2-5 minutes of work with exact code and commands. Triggers on "plan the implementation", "create a plan for", "write the implementation plan", or after /brainstorm approval.
Survey best practices from competitor ERPs and point solutions for a given feature. Use when designing new features, evaluating approaches, or understanding industry patterns. Triggers on "research best practices", "how do competitors do X", "survey the market for Y", "what's the industry standard for", or any request to understand how other systems handle a feature.
Capture a screenshot and snapshot of the current browser page when an error is encountered during e2e testing. Saves to docs/e2e/<slug>/screenshots/.
| name | design |
| description | Research-driven feature design with implementation plan. Combines brainstorming and planning into one flow. Use when designing a new feature. Triggers on "design", "brainstorm", "plan a feature", "how should we build X". |
Research competitors → design the feature → create implementation plan → get approval.
Announce at start: "I'm using the design skill."
┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
│ 1. Scope │───▶│ 2. Research│───▶│ 3. Design │───▶│ 4. Plan │
└───────────┘ └───────────┘ └───────────┘ └───────────┘
Ask focused questions (max 3-4):
Classify domain for research:
| Domain | Keywords | Competitors |
|---|---|---|
| Accounting | GL, AP, AR, invoicing | SAP, NetSuite |
| Manufacturing | Jobs, BOMs, routing | SAP, Epicor |
| MES | Tracking, scheduling | SAP, Manufacturo, First Resonance |
| CNC/Sheet Metal | Quoting, nesting | SAP, Fulcrum, Paperless Parts |
| Quality | Inspection, SPC, FAI | SAP, 1factory, HighQA |
| Inventory | Valuation, lots | SAP, NetSuite, Fishbowl |
Invoke /research [feature] to survey competitors.
Save to llm/research/[feature].md.
With research in hand, design the feature:
For each decision:
Save to docs/specs/[feature]-design.md:
# [Feature] Design
## Summary
[One paragraph]
## Research
Key findings from [llm/research/[feature].md]:
- [Pattern 1]
- [Pattern 2]
## Decisions
### [Decision 1]
**Question:** ...
**Industry:** ...
**Our Approach:** ...
## Data Model
[Tables, columns, relationships]
## Workflows
[User journeys, state transitions]
## Edge Cases
[Tricky stuff, informed by competitors]
Create implementation plan in llm/tasks/[feature]-plan.md.
Before writing tasks, load from llm/conventions/:
database.md — Migrations, RLS, transactionsforms.md — ValidatedForm, validators, actionsservices.md — Service function patternsui.md — Components, polishEach task is 2-5 minutes, one discrete action:
## Task 1: Create migration
**Files:**
- Create: `packages/database/supabase/migrations/20240115041739_add_thing.sql`
**Steps:**
1. Create migration following `llm/conventions/database.md`
2. Run: `npm run db:build`
3. Commit
| Artifact | Location |
|---|---|
| Research | llm/research/[feature].md |
| Design spec | docs/specs/[feature]-design.md |
| Implementation plan | llm/tasks/[feature]-plan.md |
Present spec and plan together. Wait for explicit approval before handing off to /execute.