Initialize, read, and update design-state.md files for Designpowers projects.
npx skills add https://github.com/Owl-Listener/designpowers --skill design-state
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
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.
Initialise the design state after the discovery brief is approved by invoking this skill.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
BasharAmsoGenerate a 14-section Game Design Document from a project concept and design brief.
jac007xCoordinate multiple validation phases into a single design QA workflow.
tdp1999Record architecture decisions with context and rationale in decisions.md.
carson-sweetRecord and track software architecture decisions in a project repository.
