openspec-feedback

Track, fix, verify, and test issues reported against an OpenSpec change.

17|7|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/gqcn/openspec-practice --skill openspec-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-feedback
Source: https://github.com/gqcn/openspec-practice/tree/main/.agents/skills/openspec-feedback
Command: npx skills add https://github.com/gqcn/openspec-practice --skill openspec-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, fix, verify, and test issues reported against an OpenSpec change, ensuring a unified workflow and traceable task management.

Core Features & Use Cases

  • Capture issues reported against OpenSpec changes
  • Append issues to the active change and create tasks, update delta specs, and plan tests
  • Facilitate end-to-end verification and regression testing with openspec-e2e workflows

Quick Start

Begin by recording the issue under the active change and proceed through the defined workflow.

Frequently Asked Questions about openspec-feedback

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

FAQPage Schema
How do I track and fix bugs reported against an active spec change?

To track bugs against an active change, record the issue and append it to tasks.md. The workflow then updates delta specs for spec-level issues and validates fixes using end-to-end tests.

What is the best way to manage task updates when spec-level changes require new test coverage?

Managing spec-level changes involves updating delta specs and planning tests. The workflow appends reported issues to the active change, creates tasks, and facilitates end-to-end verification and regression testing.

Does the OpenSpec feedback loop work with end-to-end testing workflows?

The OpenSpec feedback loop works with end-to-end testing workflows by facilitating end-to-end verification and regression testing via openspec-e2e and related skills after fixes are applied.

Can I use this workflow to capture gaps and defects found during active iterations?

You can use this workflow to capture gaps and defects during active iterations. It tracks issues reported against existing implementations across iterations and appends them to the active change.

Why do I need a delta spec when fixing a reported spec-level issue?

A delta spec is needed when fixing spec-level issues to document the required changes. The workflow updates delta specs to reflect the modifications before validating the fix with end-to-end tests.