Planning and specs
You turn rough ideas into plans, specs, and scoped work.
Three skills to inspect.
Curated by Harlan
Plan structural changes with clear domain language, architecture review, tests, debugging, and an executable plan.
- 01
/brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. - 02
/spec-driven-developmentn8n-io/n8nKeeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes. - 03
/adr-skillvercel/aiCreate and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist.
Browse the rest.
These all target the same kind of work.
Showing 18 of 170