Blueprint

Purpose

Use this skill when a product, UI, or workflow decision needs a stable decision surface before implementation.

Trigger

• A feature touches user flows, screens, copy, navigation, forms, dashboards, or visual hierarchy
• Multiple implementation lanes need one agreed product/interface contract
• Acceptance criteria exist, but the desired interaction states or content hierarchy are still fuzzy
• A redesign or frontend change needs accessibility and responsive behavior called out before coding

Workflow

• Identify target users, core job, success signal, and non-goals.
• Map the primary workflow from entry through success and recovery paths.
• Define interface decisions by surface, including empty, loading, error, disabled, and success states.
• Capture content hierarchy, navigation, controls, responsive behavior, and accessibility constraints.
• Mark assumptions and open questions separately from firm decisions.
• Attach implementation owners, affected files or surfaces, and verification evidence.
• Recommend whether to persist the result to .omg/state/blueprint.md before team-plan or team-prd.

Output Template

## Product Frame
- Target users:
- Core job:
- Success signal:
- Non-goals:

## Workflow Map
| Flow | Entry | Steps | Exit / Success | Failure / Recovery |
| --- | --- | --- | --- | --- |

## Interface Decisions
| Surface | Decision | Rationale | State Coverage | Owner | Evidence |
| --- | --- | --- | --- | --- | --- |

## Content / IA
- ...

## Accessibility / Responsiveness
- ...

## Open Questions
- ...

## Handoff
- Recommended next command:
- Taskboard sync:
- Verification notes: