Workflow: Iterating with Feedback

Your feedback becomes the next spec. Write bugs and feature requests as spec sections, and agents read them, fix them, and mark them done. No context is lost between testing, reporting, and fixing.

The Feedback-as-Spec Pattern

Instead of using a separate issue tracker, write feedback directly as spec sections. Create a section called “Bugs” or “Feedback v1.1” and list each item. This keeps feedback in the same place the agent reads from — the spec is the single source of truth.

Example feedback section

# Feedback v1.0

## Bugs
- [ ] Login form doesn't show error on wrong password
- [ ] Dashboard chart doesn't resize on mobile
- [ ] API returns 500 when project name has special characters

## Feature Requests
- [ ] Add dark mode toggle to settings
- [ ] Show last-edited timestamp on each section

Iterate Prompts

Open the prompt library and select the Iterate tab:

  • Iterate & Fix—Agent reads a feedback/bugs section, addresses each item, and marks them done as it goes.
  • Address Section—Agent addresses a single section's changes without rebuilding everything — ideal for incremental fixes.

The Feedback Loop

The loop closes when the agent reads your feedback, fixes each item, and marks them complete. Here's the typical workflow:

  1. Test the built application and note issues
  2. Create a feedback section in Supaspec with each bug or feature request as a checklist item
  3. Use an Iterate prompt — the agent reads the feedback and addresses each item
  4. The agent marks items done (✅) and updates section status
  5. Review the changes and repeat if needed

This is the key differentiator: feedback never leaves the spec. Every agent that connects next will see the full history of what was reported and what was fixed.

Structuring Feedback Sections

Tips for effective feedback sections:

  • Use Markdown checklists (- [ ]) so agents can mark items done
  • Group by category: Bugs, Feature Requests, UI Polish, Performance
  • Be specific: include routes, component names, expected vs. actual behavior
  • Version your feedback sections (e.g., “Feedback v1.0”, “Feedback v1.1”) to track iterations
← Building from SpecsAssets & Secrets →