Repository navigation
Define the cast-through-accept planning ontology and versioned artifact schemas #1649
Description
Parent epic: #1648
Outcome
Define a versioned, machine-readable contract for intent, research findings, triage dispositions, decisions, program plans, implementation plans, validation results, and acceptance state.
Requirements
- Preserve provenance to the root intent and separate findings from accepted work.
- Represent initiative, epic, feature/user story, task, milestone, dependency, size, risk, priority, owner, and acceptance criteria.
- Define
XS,S,M,L, andXL;XLwork normally requires decomposition before activation. - Define GitHub-native mappings and fallbacks when issue types, milestones, Projects, or dependency APIs are unavailable.
- Version the schema and compatibility behavior.
Acceptance criteria
- Schemas reject unresolved references and invalid values.
- Every work item traces to intent or a triaged finding.
- Exclusions and deferred findings remain auditable without becoming work items.
- Existing
/squad planoutput has a deliberate migration path. - Documentation includes an Aspiregregator example.
Size: M
Activity
bradygaster commentedon Aug 8, 2026
E2E evidence: required lifecycle markers are omitted
Tested SHA:
47e04dc73663cba40b47f00dd8e2ac42c37f6419Consumer: https://github.com/bradygaster/squad-planning-e2e
Root intent: https://github.com/bradygaster/squad-planning-e2e/issues/2
Prerequisites / reproduction
bradygaster/squad/workflows/squad.md@47e04dc73663cba40b47f00dd8e2ac42c37f6419withgh aw addand compile strictly.Expected
Each phase starts with the versioned HTML marker required by the pinned workflow (
squad-research-v1,squad-triage-v1,squad-program-v1,squad-implementation-v1,squad-validation-v1,squad-scope-accepted-v1,squad-impl-accepted-v1,squad-activated-v1) and lifecycle summary comments carrysquad-lifecycle-state.Actual
None of those required markers appeared. Representative runs/comments:
Later phases succeeded only by heuristic recognition of headings/content. Repeated activation happened to remain idempotent, but the machine-readable contract was absent.
Impact
Cross-run artifact discovery, revision selection, invalidation, and downstream automation depend on model heuristics instead of a versioned schema. This weakens deterministic validation and makes acceptance/activation drift harder to detect.
fix(gh-aw): enforce first-line marker requirement in all planning mod…
feat(gh-aw): define planning ontology and artifact schemas (#1649)
fix(gh-aw): enforce first-line marker requirement in all planning mod…
feat: Evolve Squad planning into executable SDLC lifecycle (github#1648…