P0: Task Steward discovers work and launches GitFlow RAGE/ADARD implementation #1

New issue

Closed

opened 2026-08-26 08:41:33 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-26 08:41:33 +00:00

(Migrated from github.com)

Goal

Add a reusable Task Steward workflow to RAGE that discovers/selects actionable repository work, analyzes the owning repository before mutation, creates a GitFlow feature branch, then runs the implementation phase through RAGE using an ADARD record and TDD-first execution.

Required flow

Discover candidate work from remote GitHub issues/PRs using explicit repository/label/query policy.
Select one bounded candidate deterministically; never invent work when no candidate matches.
Before implementation, inspect the owning repository's current remote default branch, applicable AGENTS.md/repo instructions, issue/PR discussion, relevant source/tests, and open conflicting work.
Create a GitFlow-style feature branch from the exact current remote default-branch SHA; do not implement directly on main/master.
RAGE owns the implementation gate. The active implementation record must capture ADARD phases: Analyze, Design, Adversarial Review, Decision gate, Realize/Develop TDD-first, Verify/Evaluate.
Tests are written/committed before production implementation for coding slices where feasible. Never weaken tests or false-green.
Exact-head CI and repository-native verification determine completion evidence; merge is a separate gate.
Task Steward coordinates work selection only; it does not become runtime/product authority and does not edit unrelated repos.

Initial consumer

lost-rob0t/quasar#61 — Auto-Dig persistence backend (filesystem + existing Tek9) and StarIntel-style initfile configuration.

TDD

Add regression tests for dry-run candidate selection, deterministic ranking, no-match behavior, branch-plan output, required ADARD/RAGE phases, and refusal when repository instructions/current head are unresolved.

Non-goals

no Bixby-specific implementation
no direct writes to product default branches
no replacement for repository-native tests or GitHub review/merge gates
no hidden scheduler requirement; Task Steward must be invokable as a one-shot workflow and schedulable externally.

## Goal Add a reusable Task Steward workflow to RAGE that discovers/selects actionable repository work, analyzes the owning repository before mutation, creates a GitFlow feature branch, then runs the implementation phase through RAGE using an ADARD record and TDD-first execution. ## Required flow 1. Discover candidate work from remote GitHub issues/PRs using explicit repository/label/query policy. 2. Select one bounded candidate deterministically; never invent work when no candidate matches. 3. Before implementation, inspect the owning repository's current remote default branch, applicable `AGENTS.md`/repo instructions, issue/PR discussion, relevant source/tests, and open conflicting work. 4. Create a GitFlow-style feature branch from the exact current remote default-branch SHA; do not implement directly on main/master. 5. RAGE owns the implementation gate. The active implementation record must capture ADARD phases: Analyze, Design, Adversarial Review, Decision gate, Realize/Develop TDD-first, Verify/Evaluate. 6. Tests are written/committed before production implementation for coding slices where feasible. Never weaken tests or false-green. 7. Exact-head CI and repository-native verification determine completion evidence; merge is a separate gate. 8. Task Steward coordinates work selection only; it does not become runtime/product authority and does not edit unrelated repos. ## Initial consumer `lost-rob0t/quasar#61` — Auto-Dig persistence backend (`filesystem` + existing Tek9) and StarIntel-style initfile configuration. ## TDD Add regression tests for dry-run candidate selection, deterministic ranking, no-match behavior, branch-plan output, required ADARD/RAGE phases, and refusal when repository instructions/current head are unresolved. ## Non-goals - no Bixby-specific implementation - no direct writes to product default branches - no replacement for repository-native tests or GitHub review/merge gates - no hidden scheduler requirement; Task Steward must be invokable as a one-shot workflow and schedulable externally.