design-state

Initialize, read, and update design-state.md files for Designpowers projects.

234|55|Updated Mar 18, 2026

Search Tags:#workflow #collaboration #traceability #state-management #decisions-log #design-brief #design-state

Ready to run

npx skills add https://github.com/Owl-Listener/designpowers --skill design-state

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-state
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The design state is a living, project-wide document that records decisions, ensuring every Designpowers agent reads from and writes to a single source of truth.

Core Features & Use Cases

Maintains a per-project design-state.md file that aggregates decisions and notes
Supports initialisation, read, update, and review phases to keep the state current
Provides an artefact index and decisions log to facilitate traceability and critique

Quick Start

Initialise the design state after the discovery brief is approved by invoking this skill.

Frequently Asked Questions about design-state

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

FAQPage Schema

How do I maintain a single source of truth for design decisions across multiple agents?▼

You maintain a single source of truth by using a living design-state.md file that aggregates decisions and notes, ensuring every project agent reads from and updates one shared record.

What is a design state document and when do I need it in my workflow?▼

A design state document is a living project-wide record of decisions needed when multiple agents collaborate, ensuring traceability and consistency before starting work, during handoffs, and after task completion.

How do I set up project traceability and a decisions log for design collaboration?▼

Project traceability and a decisions log are set up by initializing a design-state.md file at the project root, which provides an artifact index and historical record after your design brief is approved.

Do I need an approved design brief before initializing design state management?▼

Yes, an approved design brief is required to initialize, read, and update the design state, ensuring the project has validated foundational requirements before tracking decisions and artifacts.

When should I update the design state during agent handoffs?▼

The design state should be updated before starting work, before agent handoffs, and after each agent completes work, allowing them to read, append, and update decisions and artifacts continuously.

What are the limitations of using a markdown file for design state management?▼

Using a markdown file for design state management requires a design-state.md file strictly at the project root and depends on an approved design brief, meaning initialization and updates fail without these prerequisites.