Stack Workflow Grill Status

Branch Dashboard

Parked Branches

• Cross-repo stacking between /Users/stefan/Desktop/repos/wearedevpunks-skills and Harness is parked unless the team wants source-repo and downstream-sync PRs stacked across two repositories. Current assumption: keep cross-repo ordering as a runbook, not a single stack.

Glossary

Terms

• Stack-aware PR: A PR whose base branch intentionally represents its dependency relationship, allowing stack sync to infer or repair the chain. Avoid: always-stacked PR, fake stack.
• Stack root: The oldest open PR branch in a stack, normally based on trunk.
• Stack descendant: An open PR branch based on another open PR branch.
• Stack sync: The stack sync --dry-run then stack sync workflow that inspects, records, repairs, retargets, and updates stack metadata.
• Task Dependency: An implementation ordering relationship inside one epic/plan and normally inside one PR. Avoid: PR stack dependency.
• Backlog Dependency: An epic/story dependency that may require a new spec or PR to build on work from another open PR.
• Branch/Base Intent: A spec-level record of the intended git branch, PR base branch, parent PR evidence, and required stack gate for backlog-dependent work.
• No Stack Required: A spec-level dependency result used when a backlog dependency is already merged or otherwise proven implemented, so the new PR can be based on trunk.
• Dependency Readiness Gate: The create-spec check that proves backlog dependencies are implemented, represented by an open parent PR, or blocking.
• Implemented-Status Artifact: Existing dependency IMPLEMENTATION-NOTES.md or equivalent artifact that records implementation completion.
• Code Evidence: Local code paths/behavior or merged PR evidence proving the dependency landed when no implemented-status artifact exists.
• Implementation Branch Gate: The implement-spec pre-coding check that verifies or creates the intended child branch from recorded Branch/Base Intent.
• PR-After-Implementation: The default delivery order where implementation, commit, push, and PR creation/update happen before stack sync.
• Stack Cleanliness Gate: The delivery closeout check requiring stack status and stack sync --dry-run, plus stack sync when pending stack changes exist.
• Stack Tool Availability: The required-tool condition for stack-dependent planning/delivery workflows.
• Dependency Readiness Section: The spec/plan section with Status, Dependency, Evidence, and Reason for backlog dependencies.
• Branch/Base Intent Section: The spec/plan section with Parent PR, Parent branch, Child branch, PR base, and Required gate for stack-dependent work.
• Phase Skill Enforcement: The rule that stack behavior lives in the relevant phase skills, not generic prompt slogans.
• Skills-First Stack Docs: The documentation policy that phase skills and the local stack skill are canonical unless manual operator usage later needs a runbook.

Relationships

• A Stack descendant depends on exactly one immediate parent branch.
• A Stack root belongs to one stack and is based on trunk.
• A Stack-aware PR may be independent when based on trunk or dependent when based on another PR branch.
• A Task Dependency belongs to one plan and does not imply multiple PRs.
• A Backlog Dependency may become a Stack-aware PR relationship when the dependency is represented by an open PR.
• Branch/Base Intent is recorded by create-spec and executed later by delivery or implementation flow.
• No Stack Required still requires dependency implementation evidence.
• Dependency Readiness Gate runs before stack-specific branch/base intent is finalized.
• Implemented-Status Artifact is sufficient proof of implemented dependency readiness.
• Code Evidence is fallback proof when no implemented-status artifact exists.
• Implementation Branch Gate executes Branch/Base Intent before coding starts.
• PR-After-Implementation supplies GitHub base metadata before stack sync runs.
• Stack Cleanliness Gate belongs to delivery, while review only reports stack evidence.
• Stack Tool Availability blocks only workflows that require Branch/Base Intent or stack repair.
• Dependency Readiness Section appears whenever backlog dependencies exist.
• Branch/Base Intent Section appears only for stack-dependent work.
• Phase Skill Enforcement is canonical for agent behavior.
• Skills-First Stack Docs avoids a standalone human runbook until manual usage requires one.

Axioms

• PR bases should be the source of truth for ordinary stack inference.
• stack sync --dry-run is the inspection entrypoint before stack mutation.
• Intra-epic task dependencies do not create separate PRs by default.
• create-spec owns the first stack decision for new backlog-driven work.
• create-spec records stack intent; it does not mutate git state by default.
• Dependency readiness is a create-spec gate, not a stack feature.
• If a backlog dependency is neither proven implemented nor represented by an open parent PR, spec creation blocks.
• SPEC.md and PLAN.md prove intent, not implementation.
• IMPLEMENTATION-NOTES.md or an equivalent implemented-status artifact is trusted as sufficient readiness proof.
• create-plan preserves and validates stack/dependency decisions; it does not decide stack topology.
• implement-spec may create or switch branches automatically when Branch/Base Intent is recorded.
• PR creation defaults to after implementation; early draft PRs are opt-in.
• stack sync runs after PR base metadata exists.
• Delivery owns stack mutation and cleanliness; review reports stack evidence only.
• Missing stack blocks stack-dependent workflows, not independent trunk-based work.
• Dependency Readiness is present whenever backlog dependencies exist; Branch/Base Intent appears only for stack-dependent work.
• Do not duplicate stack workflow behavior in root AGENTS.md or scaffolded prompt guidance when phase skills already enforce it.
• Stack workflow docs are skills-first; no standalone human runbook is needed initially.

Flagged Ambiguities

• "Always on stack mode" can mean either every PR is inspected by stack or every PR is forcibly tracked. Current leaning: every PR workflow is stack-aware, but only dependent PRs form stacks.
• "depends_on" was used to mean both task ordering and PR dependency. Resolution: task-level depends_on stays inside one PR; backlog dependency can drive stacked PR branch/base intent.
• "missing parent PR evidence" does not always mean stack failure. Resolution: if dependency is proven merged/implemented, record No Stack Required; otherwise block spec creation.
• "documentation" was used to include both agent enforcement and human reference. Resolution: agent enforcement belongs in phase skills, not root AGENTS.md; no standalone human runbook is needed initially.