writing-design-plans

Breaks approved design directions into discrete tasks with acceptance criteria and accessibility considerations.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill writing-design-plans-owl-listener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-design-plans
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill writing-design-plans-owl-listener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks an approved design direction into discrete, reviewable tasks with explicit verification criteria, enabling predictable progress and traceability.

Core Features & Use Cases

  • Divides design work into small, independently reviewable tasks with clear acceptance criteria.
  • Embeds task sizing (2-5 minutes) and accessibility considerations within each task.
  • Saves and references plans to docs/designpowers/plans/YYYY-MM-DD-<feature>-plan.md and integrates with discovery/strategy workflows.

Quick Start

Provide an approved design direction and request a step-by-step plan with verification criteria for each task.

Frequently Asked Questions about writing-design-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break an approved design direction into actionable tasks?

To break an approved design direction into actionable tasks, divide the work into discrete, independently reviewable items with explicit acceptance criteria, accessibility considerations, and 2-5 minute sizing for predictable progress.

What is design task sizing and how does it improve design planning?

Design task sizing estimates task duration within a 2-5 minute range to create predictable, traceable design plans. It improves design planning by ensuring each task is small enough for independent review and explicit verification.

How do I add accessibility considerations to a design implementation plan?

To add accessibility considerations to a design implementation plan, weave accessibility requirements directly through each discrete task alongside explicit verification criteria and sizing, ensuring traceability throughout the design workflow.

Can I use design planning for strategy handoffs and implementation scoping?

Yes, you can use design planning for strategy handoffs and implementation scoping by applying it to design discovery. It breaks down approved directions into verifiable tasks saved as structured markdown documentation.

What is the best way to document design plans with explicit verification criteria?

The best way to document design plans with verification criteria is to save them as structured markdown files using a dated naming convention like YYYY-MM-DD-feature-plan.md, ensuring saved documentation integrates with discovery workflows.

Why do my design plans lack traceability during implementation?

Design plans lack traceability during implementation when tasks lack explicit acceptance criteria and discrete sizing. Applying structured verification criteria to each task ensures predictable progress and traceability from strategy to execution.