Use this when a demo or showcase is done and you have raw feedback to process. This is the companion to /demo-prep — one prepares for the demo, this one processes what comes out of it. Produces categorized feedback with recommended backlog actions.
Process
Step 1: Gather demo feedback
Ask the user to provide:
- Demo/showcase notes — raw notes, transcript, or summary from the demo. Paste directly.
- What was demonstrated — list of features or stories shown during the demo.
- Who attended — stakeholders, their roles, their relationship to the work (optional but improves categorization).
Step 2: Categorize feedback
For each piece of feedback, categorize as:
- Positive validation — confirms the work meets expectations. No backlog action needed, but document for stakeholder reporting.
- Scope suggestion — request to expand or modify what was shown. Needs assessment: is this a new story, a change to an existing story, or out of scope?
- Missed expectation — something that should have been there but wasn't. Might be a bug, a missed AC, or a scope gap.
- New idea — sparked by seeing the work but not related to what was demonstrated. Capture for backlog consideration.
Step 3: Structured output
## Demo Feedback Analysis — (date)
### What Was Demonstrated
- (feature/story 1)
- (feature/story 2)
### Feedback Summary
| # | Feedback | Category | From | Recommended Action |
|---|----------|----------|------|--------------------|
| 1 | (feedback) | Validation/Scope/Missed/New Idea | (who) | (action) |
### Positive Validations
- (what was validated) — (who validated it)
(Use for /artbeat and stakeholder updates)
### Scope Suggestions — Requires PM Decision
- (suggestion) — Recommend: New story / Update existing (key) / Out of scope
- Rationale: (why this categorization)
### Missed Expectations — Likely Bugs or Gaps
- (missed item) — Recommend: Bug / Missing AC on (story key) / Scope gap
- Severity: (blocking / degraded / cosmetic)
### New Ideas — Backlog Candidates
- (idea) — Confidence: High/Med/Low
- (context: why this came up, who suggested it)
### Recommended Next Steps
- (items ready for /story-write)
- (items that need clarification first)
- (items to add to /artbeat as wins)
Step 4: Review
Ask the user:
- Are the categories right? Any miscategorized items?
- For scope suggestions: which ones do you want to pursue vs. defer vs. reject?
- Any missed expectations that are actually intentional scope exclusions?
Remember: this draft multiplies your output, not your judgment. You own the final narrative.
Output
Present the analysis as formatted text in the conversation. The user decides which items proceed to /story-write or other skills.
Example Output
Input
- Demo/showcase notes: "Sarah loved the new filtering — said it was exactly what her team asked for. Marcus asked why the export doesn't include the date range in the filename, said it's confusing when they download multiple files. Priya flagged that the 'Save Filter' button isn't persisting after page refresh — she tried it twice. Dev lead Ravi mentioned it would be cool if filters could be shared via URL so teams could bookmark views. Marcus also asked if we could add a column for 'Last Modified By' in the results table — said finance has been requesting that for months. General applause on the dashboard load time improvement."
- What was demonstrated: Advanced filter panel with multi-select, Export to CSV functionality, Dashboard performance improvements (load time reduced from 8s to 1.2s)
- Who attended: Sarah Chen (VP of Operations, primary sponsor), Marcus Webb (Finance Director, power user), Priya Nair (QA Lead, internal), Ravi Desai (Dev Lead, internal)
- Demo date: June 11, 2025
Output
Demo Feedback Analysis — June 11, 2025
What Was Demonstrated
- Advanced filter panel with multi-select
- Export to CSV functionality
- Dashboard performance improvements (load time 8s → 1.2s)
Feedback Summary
| # | Feedback | Category | From | Recommended Action |
|---|---|---|---|---|
| 1 | Filter panel is exactly what the team asked for | Validation | Sarah Chen | Document for stakeholder update |
| 2 | Export filename doesn't include date range — confusing with multiple downloads | Missed Expectation | Marcus Webb | Review export AC; likely missing AC on DASH-47 |
| 3 | 'Save Filter' not persisting after page refresh | Missed Expectation | Priya Nair | Log as bug; blocking intended behavior |
| 4 | Filters shareable via URL for team bookmarking | New Idea | Ravi Desai | Capture as backlog candidate |
| 5 | Add 'Last Modified By' column to results table | Scope Suggestion | Marcus Webb | Assess as new story; finance demand signals priority |
| 6 | Dashboard load time improvement noted positively | Validation | (room) | Document for stakeholder update |
Positive Validations
- Advanced filter panel meets expectations — Sarah Chen (VP of Operations)
- Dashboard performance improvement recognized positively — full room (Use for /artbeat and stakeholder updates)
Scope Suggestions — Requires PM Decision
- 'Last Modified By' column in results table — Recommend: New story
- Rationale: Not adjacent to any story shown in this demo; represents a net-new data display requirement. Finance demand noted by Marcus suggests real business pull. Needs data availability check before writing.
Missed Expectations — Likely Bugs or Gaps
- Export filename missing date range — Recommend: Missing AC on DASH-47
- Severity: Degraded — exports still function, but usability is impaired for multi-file workflows
- 'Save Filter' not persisting after page refresh — Recommend: Bug
- Severity: Blocking — persistence is the core value of the Save Filter feature; non-functional as shipped
New Ideas — Backlog Candidates
- Shareable filter URLs — Confidence: Med
- Ravi raised this organically after seeing multi-select in action. Suggests teams would use saved filter states collaboratively. Needs UX and auth/permission scoping before sizing.
Recommended Next Steps
- Ready for /story-write: 'Last Modified By' column (pending data availability confirmation); Shareable filter URLs (after scoping conversation with Ravi)
- Needs immediate action: File bug for Save Filter persistence — confirm severity with Priya before next sprint planning
- Review AC: DASH-47 export story — determine if date range in filename was implied or omitted; update AC before closing the story
- Add to /artbeat as wins: Filter panel stakeholder validation from primary sponsor; dashboard load time improvement (8s → 1.2s)
Categories look right? Flag anything that's actually an intentional exclusion — particularly the export filename, which may have been a known descope.