Replace Dev Loop with autonomous Issue-driven QuickDev

[mindcarver]

Outcome

Thinloop exposes scd-quickdev as the unified entry point for bugs and features, using a GitHub Issue as the requirement and acceptance source of truth and autonomously delivering eligible changes through pull request merge.

User problem

The previous scd-dev-loop name and workflow did not make bug diagnosis, requirement clarification, Issue ownership, branch isolation, PR delivery, merge responsibility, and human real-use acceptance explicit.

In scope

• Rename scd-dev-loop to scd-quickdev.
• Route clear work directly and underdefined work through scd-discovery.
• Use one GitHub Issue for requirements, acceptance, tasks, and durable delivery evidence.
• Add diagnosis-first bug handling and regression evidence.
• Require a unique task branch and use worktrees only when isolation is needed.
• Let the agent verify, self-review, create the PR, wait for checks, and merge eligible changes into main.
• Leave the Issue open as awaiting-uat for human real-use acceptance.
• Preserve human gates for high-risk merge and production deployment.
• Update all supported plugin manifests, documentation, cross-skill handoffs, continuity hooks, and tests.
• Record the autonomous delivery and reinstall default in AGENTS.md.

Out of scope

• Automatic production deployment.
• Weakening repository protections.
• Automatic merge of authentication, payment, destructive data, compliance, or other irreversible high-risk changes.
• Removing historical evaluation artifacts that intentionally reference prior skill names.

Confirmed decisions

• GitHub Issue is the sole requirement and acceptance source of truth for normal repository delivery.
• PR is the implementation, verification, audit, and rollback boundary.
• The agent owns engineering acceptance and eligible merge; the user owns real-use acceptance.
• Every meaningful task gets a unique branch; worktrees remain conditional.
• A composing Thinloop skill can impose a narrower delivery authority than standalone QuickDev.

Failure and edge cases

• Missing GitHub access blocks Issue-driven implementation instead of silently creating a local specification.
• Legacy managed_by: scd-dev-loop continuity state must surface a migration instruction rather than being ignored.
• If merging main deploys production, merge requires the production approval gate.
• Evolve trials and other bounded composed workflows must not inherit standalone QuickDev push or merge authority.

Acceptance

• A1: scd-quickdev supports direct, clarify, and discovery paths.
• A2: Bug work records symptom, expectation, diagnosis status, and regression evidence.
• A3: Issue, branch, worktree, PR, merge, and UAT responsibilities are explicit.
• A4: Discovery creates an approved GitHub Issue instead of .scd/specs.
• A5: Codex, Claude Code, OpenCode, WorkBuddy, and ZCode manifests expose version 0.7.0 and seven current skills.
• A6: Legacy continuity state is migrated safely.
• A7: Repository and global AGENTS.md record the autonomous delivery default.
• A8: Full tests and plugin/skill validators pass.

Implementation tasks

• Implement and document QuickDev.
• Update Discovery and composed skills.
• Update manifests, hooks, README, and UI metadata.
• Add contract and migration tests.
• Add AGENTS.md delivery defaults.
• Commit, push, create PR, merge main, and reinstall local agents.

Verification

• Tests: node --test tests/*.test.mjs passed 89/89 on merged main.
• Delivery: PR Add autonomous Issue-driven QuickDev delivery #2 merged to main at 7385e21241750e1374461808a67e20da655dc7bb; local and remote main match.
• Codex: seven current source-linked skills present; legacy and malformed links absent.
• Claude Code: thinloop@thinloop version 0.7.0, enabled; application restarted.
• OpenCode: runtime discovery reports all seven current scd-* skills including scd-quickdev and no legacy entry.
• WorkBuddy: thinloop@thinloop version 0.7.0, enabled; application restarted.
• ZCode: application UI reports version 0.7.0, seven current skills including scd-quickdev, and two hooks (SessionStart, Stop).
• Instructions: project AGENTS.md is committed; global /Users/carver/.codex/AGENTS.md contains the same autonomous delivery default.

Current status

awaiting-uat — engineering delivery is complete. The Issue remains open for human real-use acceptance. The repository does not currently define an awaiting-uat label, so the status is recorded here instead of inventing a new label.

Unknowns

• None.

[mindcarver]

Engineering delivery complete; status is awaiting-uat.

• PR: Add autonomous Issue-driven QuickDev delivery #2 (merged)
• Main SHA: 7385e21241750e1374461808a67e20da655dc7bb
• Tests: 89/89 passed on merged main
• Reinstalled/refreshed: Codex, Claude Code, OpenCode, WorkBuddy, ZCode
• Verified: version 0.7.0, seven current skills, scd-quickdev present, legacy scd-dev-loop absent from current installs

This Issue remains open for human real-use acceptance. No awaiting-uat repository label exists, so the state is recorded in the Issue body and this comment.