polish

Run a guided iteration interview and append a new iteration checklist to the current sprint file.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/zabuuq/sdd-plugin --skill polish-zabuuq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/polish
Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill polish-zabuuq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you turn completed sprint work into a better, more reliable outcome by scoping a focused improvement round (fixes, UX tweaks, and small feature additions) without destabilizing the broader plan.

Core Features & Use Cases

  • Guided iteration interview: Runs a brief, structured conversation to clarify what to polish and to produce actionable checklist items.
  • Guardrailed sprint readiness: Blocks polishing until all sprint checklist items are complete, unless the sprint has been explicitly re-opened via the close-sprint manifest mechanism.
  • Living-documents discipline: Uses the living-documents protocol to avoid direct edits to approved scope/PRD/spec, routing changes into backlog/unvetted flow instead.
  • Sprint artifacts updated safely: Appends a new ## Iteration N section to docs/sprint-N.md, updates docs/open-concerns.md, writes process notes to process-notes-sprint-N.md, and cleans up any polish resume file.

Quick Start

Tell your AI to run /sdd:polish to interview you about what to improve and append the next iteration checklist to your current sprint.

Frequently Asked Questions about polish

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

FAQPage Schema
How do I improve sprint results and add UX improvements without destabilizing project scope?

To improve sprint results safely, run a guided iteration interview that scopes focused improvements like bug fixes and UX tweaks. This process appends a new iteration checklist to your sprint file while keeping project scope stable by routing changes into backlog flow instead of direct edits.

What is the best way to add small features after a sprint build is completed?

Adding small features after a build requires a polish iteration that runs a structured interview to clarify improvements. It appends actionable checklist items to your current sprint file, ensuring that new additions do not destabilize the broader approved plan.

Can I polish a closed sprint if the checklist items are not fully complete?

You cannot polish a closed sprint with incomplete checklist items unless the sprint is explicitly re-opened. The system uses a close-sprint manifest mechanism as a guardrail to block polishing until all items are complete, preventing uncontrolled scope changes.

How does living-documents compliance affect sprint artifact updates during an iteration?

Living-documents compliance ensures sprint artifacts are updated safely by preventing direct edits to approved scope or PRD. Instead, changes are routed into a backlog or unvetted flow, and the process appends iteration sections to sprint files while logging updates to open concerns and process notes.

What startup state is required before running a sprint polish iteration?

Running a sprint polish iteration requires loading the startup state, which includes the user profile, current project state, and the specific sprint file. This ensures the guided interview has the necessary context to append accurate checklist items and process notes.