What problem does it solve? Implementing user stories without a structured process leads to untracked progress, unreviewed code, orphaned Git worktrees, and issues closed before their pull requests merge. This Skill enforces a complete, auditable story lifecycle from initialization through teardown. ## Core Features & Use Cases - Isolated Worktree Workflow: Provisions dedicated Git worktrees via wt (worktrunk) based on origin/staging, then reaps processes and removes them after PR submission. - Dual-Role Feedback Loop: Coordinates an Implementor and an SME Reviewing Judge who validates architectural intent, adjudicates scope, and monitors CI via gh pr checks. - GitHub Audit Trail: Mandates periodic progress comments, bidirectional PR-to-issue linking with Fixes keywords, high-detail completion summaries, and PR-merge-gated issue closure. - Use Case: An agent picks up story 2.3 (Product Filter Component), creates a worktree, implements and verifies with pnpm run verify:local, passes SME review, opens a PR targeting staging, posts completion documentation, and tears down the worktree. ## Quick Start Use the story-feedback-loop skill to implement GitHub issue #42 in an isolated worktree with full progress tracking and SME review.
