skills.rest
iamsteveholmes
iamsteveholmesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

quick-fix

Coordinate a five-phase single-story fix workflow with gated approvals and merge-back.

Updated Mar 10, 2026
Search Tags:#code-review#gherkin#git-worktree#story-workflow#quick-fix#avfl#gated-approval
One-click install
npx skills add https://github.com/iamsteveholmes/momentum --skill quick-fix-iamsteveholmes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-fix
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/quick-fix
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill quick-fix-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a disciplined, end-to-end workflow to fix a single story from definition through validation, with gated approvals and deterministic execution.

Core Features & Use Cases

  • Five-phase workflow: Define, Specify, Implement, Validate, Ship.
  • Deterministic governance: gating, AVFL checks, code review, and merge-back to main.
  • Use Case: when a developer needs a focused fix on one story with traceable artifacts and documented results.

Quick Start

Describe the fix you want to apply and approve each gate to start Phase 1.

Frequently Asked Questions about quick-fix

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

FAQPage Schema
How do I execute a single-story fix end-to-end with gated approvals?▼

A single-story fix is executed end-to-end by progressing through five phases: Define, Specify, Implement, Validate, and Ship. This enforces gated approvals and deterministic execution from definition through final shipping.

How does a Gherkin feature specification work within a story workflow?▼

A Gherkin feature specification defines acceptance criteria during the Specify phase of the story workflow. This translates story requirements into structured, testable scenarios before implementation begins in the worktree.

What is the best way to manage a code review and merge-back to the main branch?▼

Managing merge-back to main requires deterministic governance steps including enforced code review and post-merge validation. This ensures only reviewed changes are merged back to the main branch after implementation.

Do I need a git worktree to isolate a story fix during implementation?▼

Yes, the implementation phase of the story workflow uses a git worktree to isolate changes. This keeps the single-story fix contained and traceable from specification through post-merge validation.

When should I use a five-phase story workflow instead of direct commits?▼

Use a five-phase story workflow when a developer needs a focused fix on one story with traceable artifacts and documented results. It provides deterministic governance via gating, AVFL checks, code review, and merge-back to main.

Related Skills

Explore More Software Engineering Skills→
humansyshumansys
71

rai-story-run

Orchestrate RaiSE story lifecycles across detection, design, implementation, review, and closure phases.

Official
Advanced
MelvynxMelvynx
223

merge

Automate Git branch merges with context-aware conflict resolution.

Community
Advanced
kinncjkinncj
23

spec-kit

Convert feature ideas into Gherkin story files with frontmatter status tracking.

Community
Intermediate
TurnaboutHeroTurnaboutHero
12

git-master

Enforce atomic commits and branching strategies for Git workflows.

Community
Basic