Product & Design
Design Spec Writer
Design Spec Writer turns design & ux material into a draft package with a concrete design user-task friction map, spec accessibility and state coverage check, and product design handoff recommendation. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for screen, flow, copy, or design spec, target user and task context, and accessibility, responsive, and content constraints up front, then organizes the output around design, spec, and product. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. Design Spec Writer is scoped to the Design & UX workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.
One-Time Purchase
$19.99
Design Spec Writer — Sample Brief
Headline
Builds a design review artifact for design spec writer work, turning screen, flow, copy, or design spec, target user and task context, and accessibility, responsive, and content constraints into design user-task friction map, spec accessibility and state coverage check, and product design handoff recommendation. In this example, Northbeam Analytics needs a reviewer-ready draft package built from supplied notes, constraints, and approval context. The output is a concrete draft package: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| screen, flow, copy, or design spec | Northbeam Analytics needs a reviewer-ready draft package built from supplied notes, constraints, and approval context. | Provided |
| target user and task context | Three representative examples from the current workflow | Reviewed |
| accessibility, responsive, and content constraints | Approval threshold and final reviewer | Confirm |
| design owner and acceptance criteria | Design & UX owner and downstream audience | Ready |
Design Evidence Model
| Field | What must be captured | Review consequence |
|---|---|---|
| Design signal | Tie findings to user task, viewport or state, accessibility expectation, and handoff acceptance rule. | Treat as draft until design user-task friction map is source-backed. |
| Design User Task Friction Map | Separate visual preference from usability, content, and accessibility defects. | Escalate when design evidence is missing or contradicted. |
| Spec Accessibility And State Coverage Check | Include reproduction or inspection notes that design and engineering can verify. | Reviewer resolves product design handoff recommendation before final use. |
Design Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| Design depth | Tie findings to user task, viewport or state, accessibility expectation, and handoff acceptance rule. | Keep, revise, or ask a targeted follow-up |
| Spec boundary | Separate visual preference from usability, content, and accessibility defects. | Confirm this is not a renamed adjacent bundle skill |
| Writer handoff | Include reproduction or inspection notes that design and engineering can verify. | Assign the owner decision before final use |
Design Spec Writer Work Map
Design Spec Writer focus areas
Draft Draft Package
| Design signal | Design User Task Friction Map | Spec Accessibility And State Coverage Check | Product Design Handoff Recommendation | Spec decision |
|---|---|---|---|---|
| Design | design user-task friction map | spec accessibility and state coverage check | product design handoff recommendation | Keep if source-backed |
| Spec | design user-task friction map | spec accessibility and state coverage check | Design evidence is missing or contradicted. | Revise missing evidence |
| Product | Tie findings to user task, viewport or state, accessibility expectation, and handoff acceptance rule. | Separate visual preference from usability, content, and accessibility defects. | product design handoff recommendation | Assign owner decision |
Use now
Design Spec Writer
Best when design & ux work needs a concrete draft package.
Hold back
Missing evidence
Best deferred when a key input would change the artifact.
Reviewer note
The output is structured so an operator can validate the draft, edit the artifact, and hand it to the next owner without re-reading the entire packet. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.
This sample illustrates the skill's output format. Companies referenced are fictional and used recurringly across sample outputs.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Design & UX
Bundle price: $55. Compare this skill with the full workflow bundle or Pro access.
Best for
Designers and PMs turning a screen or flow into an engineer-ready spec — states, behaviors, and edge cases written down so handoff does not lose intent. Most useful when design and engineering sit apart and ambiguity in the handoff turns into rework.
Not ideal for
High-fidelity visual specs that belong in Figma, and validating the underlying product decision. It documents the design — it does not decide whether the design is the right one to build.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short copy-and-configure setup in your preferred agent workspace. No custom integration is required for the skill file itself.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.