Create a written definition of done with scope and success criteria.
npx skills add https://github.com/rickmanelius/skills --skill sys-paint-done
Please help me install this Agent Skill. Skill: sys:paint-done Source: https://github.com/rickmanelius/skills/tree/main/plugins/save-your-startup/skills/sys-paint-done Command: npx skills add https://github.com/rickmanelius/skills --skill sys-paint-done
Vague or misaligned expectations between requesters and implementers cause wasted time, rework, and inconsistent results. This Skill helps teams capture a single, actionable picture of "done" before work begins so everyone builds the same thing.
Describe what "done" looks like for the feature or deliverable and let the assistant ask clarifying questions until a shared, written definition is produced.
High-intent search queries and answers about installing and using this skill.
A definition of done prevents wasted time and rework by aligning requesters and implementers on a single, actionable picture of completion before work begins. It captures scope, measurable success criteria, and verification steps to prevent inconsistent results and scope creep.
The best way to align stakeholder expectations for design handoffs is through guided clarification that iteratively surfaces hidden assumptions and edges. This produces a concise written summary with explicit boundaries, ensuring engineers and designers build the same thing without ambiguity.
Yes, you can use it to establish sprint acceptance criteria and milestone scope by defining measurable success criteria and explicit in-scope versus out-of-scope boundaries. It is ideal for iterative clarification to avoid rework and scope creep on small projects.
You prevent scope creep by capturing a shared, testable definition of done that establishes explicit in-scope versus out-of-scope boundaries before work begins. The guided clarification process surfaces hidden constraints and produces a concise written summary for verification.
You need to formalize a definition of done for a deliverable when ambiguity between requesters and implementers drives rework or delays. It is essential for product features, design handoffs, milestones, and small projects requiring measurable success criteria and verification steps.
HmbownAnalyze messages to infer subtext and suggest diplomatic replies.
deMGoncalvesDecompose large specifications into atomic implementation tasks with dependencies and acceptance criteria.
mahg-esTurn vague project ideas into a structured sprint plan with scope and ownership.
dralgorhythmClarify ambiguous product requirements using Five Whys, SMART, and edge-case analysis.
