feedback

Record sprint feedback notes to docs/sdd-feedback.md for the SDD plugin.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of letting you quickly report improvements to the SDD plugin without breaking your flow or requiring you to fill out complex forms.

Core Features & Use Cases

  • Fast feedback capture with context: Stores your note alongside the timestamp, current sprint number, and the last non-feedback command.
  • Instant return behavior: Avoids extra interviews and minimizes loaded context to keep the command responsive.
  • Optional cross-clone forwarding: Can mirror feedback into a configured plugin clone so the plugin maintainers can review it later.

Quick Start

Run /sdd:feedback with your feedback note to save it immediately to docs/sdd-feedback.md.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I capture improvement feedback without interrupting my active sprint workflow?

To capture feedback without interrupting workflow, run the feedback command with your note as an argument. It appends the entry to docs/sdd-feedback.md with the current sprint number and timestamp, then returns immediately without updating the last command state.

What context is automatically included when logging markdown improvement notes?

Markdown logging automatically includes the timestamp, current sprint number, and the previously executed non-feedback SDD command. This contextual data is stored alongside your note in docs/sdd-feedback.md to help track improvement ideas.

Can I forward captured feedback notes to a configured plugin clone for maintainers?

Yes, you can forward feedback notes to a configured clone. The command optionally mirrors the formatted markdown entry into the forwarded clone, allowing plugin maintainers to review improvement feedback captured across repositories.

Does the feedback command require a complex form or interactive interview to submit product improvement ideas?

No, the feedback command avoids complex forms and extra interviews. It reads the feedback note directly from arguments or prompts for it when absent, minimizing loaded context to keep the command responsive during active project sessions.

What happens to my last executed command state after submitting quick improvement feedback?

Your last executed command state remains unchanged after submitting feedback. The command returns immediately with no lastCommand updates, ensuring your active sprint tracking and project session flow are not disrupted.

When should I use a dedicated command workflow for cross-repo feedback forwarding instead of standard logging?

Use a dedicated command workflow for cross-repo feedback forwarding when you need to mirror improvement notes to a configured plugin clone. This ensures maintainers receive the feedback while you continue standard logging in your local repository.