Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From blueprint
Create a design document for requirements, approach, and technical decisions
npx claudepluginhub urso/claudev --plugin blueprintHow this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:design-createThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a design document that captures problem context, goals, approach, and technical decisions.
Technical design documents — problem analysis, solution exploration, architectural decisions. Invoke whenever task involves any interaction with design documents — creating, updating, reviewing, comparing options, or capturing architectural decisions.
Orchestrates design workflow from idea to docs: context gathering, clarification, brainstorming, design documentation, planning handoff. Use when starting any design process.
Generates architecture/design documents from approved SRS docs when no prior design exists, proposing 2-3 approaches with trade-offs and securing section-by-section approval.
Share bugs, ideas, or general feedback.
Create a design document that captures problem context, goals, approach, and technical decisions.
${CLAUDE_PLUGIN_ROOT}/resources/discovery.md${CLAUDE_PLUGIN_ROOT}/resources/design-operations.md${CLAUDE_PLUGIN_ROOT}/scripts/list-workflows.sh$ARGUMENTS
!bash ${CLAUDE_PLUGIN_ROOT}/scripts/list-workflows.sh "" design
Read DISCOVERY_GUIDE and DESIGN_OPS for available tools and procedures.
Read the workflow files listed in the pre-computed context above for design guidelines.
Ask clarifying questions to understand:
Get user confirmation before proceeding.
Ask user for a short kebab-case name (e.g., user-auth, api-redesign).
If related designs exist, ask user if this design depends-on any of them.
Ask user if there are project files that should be referenced by this design (e.g., source code, configs, API specs). These are project-relative paths stored in the references frontmatter field and will be auto-loaded as context during story expansion and development.
Follow the procedures in DESIGN_OPS to create the design. Fill in all sections with the gathered context.
The PostToolUse hook will automatically validate the document after writing.
Spawn the design-review agent to review the newly created design with fresh context. Pass the design file path as the argument.
/design-expand to break into stories