writing-design-plans

writing-design-plans is a skill for Claude Code from Owl-Listener/designpowers. It costs 35 tokens per session (887 once invoked), scanned A, original, MIT.

A guide for turning an approved design direction into a sequence of small, reviewable design tasks. It covers structure, layouts, components, interactions, content, and accessibility.

In plain words
What is it for?
Use it after a design brief or strategy is approved and before implementation begins. It can organize work for screens, flows, components, content, and accessibility requirements.
Why use it?
It helps make a broad design effort easier to review and implement by defining what needs to be designed and in what order.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the designpowers plugin — 36 skills, 10 agents, 1 hook shipped together

Good fit Use it after a design brief or strategy is approved and before implementation begins. It can organize work for screens, flows, components, content, and accessibility requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designpowers/writing-design-plans
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designpowers --skill writing-design-plans
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designpowers

Made for: Claude Code.

Or install designpowers, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for writing-design-plans

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designpowers/writing-design-plans/github.svg)](https://agentmods.dev/skills/owl-listener/designpowers/writing-design-plans)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designpowers/writing-design-plans"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/writing-design-plans/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for writing-design-plans

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designpowers/writing-design-plans"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/writing-design-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 887 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00887
Opus 5 $0.00017 $0.00443
Sonnet 5 $0.00007 $0.00177
Haiku 4.5 $0.00003 $0.00089

Measured 10d ago against content hash 631241ac4f4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

writing-design-plans scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/writing-design-plans/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Design Plans

A design plan breaks an approved design direction into discrete, reviewable tasks. Each task is small enough to evaluate clearly and specific enough that the result is predictable.

When to Use

  • After design-discovery and/or design-strategy have produced an approved direction
  • Before any implementation work begins
  • When a design task is too large to complete and review in one step

Process

Step 1: Review Inputs

Gather:

  • Design brief (from design-discovery)
  • Strategy document (from design-strategy, if applicable)
  • Personas (from inclusive-personas)
  • Existing design system inventory

Step 2: Identify Design Tasks

Break the work into categories:

  1. Structure tasks — information architecture, page hierarchy, navigation
  2. Component tasks — individual UI components that need designing
  3. Layout tasks — how components compose into screens
  4. Interaction tasks — states, transitions, feedback patterns
  5. Content tasks — copy, labels, error messages, help text
  6. Accessibility tasks — specific inclusive design requirements per component

Step 3: Order the Work

Design work has natural dependencies:

Structure → Layout → Components → Interactions → Content → Review
     ↑ accessibility woven through each step, not a final phase ↑

Order tasks so that:

  • Foundation work (structure, layout) comes before detail work (interactions, content)
  • Each task can be reviewed independently
  • Accessibility is addressed within each task, not deferred

Step 4: Write the Plan

# Design Plan: [Feature/Project Name]

> **For agentic workers:** REQUIRED: Use designpowers:designpowers-critique to review completed work against this plan.

**Goal:** [One sentence — what this plan delivers]

**Design Direction:** [Reference to the design brief or strategy]

**Personas:** [Reference to personas this plan serves]

---

## Task 1: [Task Name]

**Files:** [Which files will be created or modified]

- [ ] Step 1: [Specific action]
- [ ] Step 2: [Specific action]
- [ ] Step 3: [Specific action]

**Accessibility check:** [What inclusive design criteria this task must meet]

**Verification:** [How to confirm this task is complete and correct]

---

## Task 2: [Task Name]
...

Read the full file on GitHub · 120 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 120 lines · 35 tokens per session scan A 631241ac4f4f

Subscribe to this mod's changes

writing-design-plans is a skill published in the GitHub repository Owl-Listener/designpowers (245 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 887 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

accessibility-a11y

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

BlackBeltTechnology/pi-agent-dashboard · 44 tokens

tailwind-shadcn

Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.

BlackBeltTechnology/pi-agent-dashboard · 50 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

frontend-mockup-loop

Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…

BlackBeltTechnology/pi-agent-dashboard · 185 tokens

frontend-mockup-loop-dashboard

Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…

BlackBeltTechnology/pi-agent-dashboard · 83 tokens

goga-define-experience

Define the user experience required to achieve the established product goals and solve the identified problem.

qarium/goga · 6 tokens