steve/skills
Public Access
1
0
Fork 0
Code Issues 11 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Implement dependencies and frontier queries #22

New Issue
Open
opened 2026-08-17 22:01:08 -04:00 by steve · 0 comments
steve commented 2026-08-17 22:01:08 -04:00
Owner
Copy Link
Copy Source

Part of Provider-neutral tracker automation CLI and library

Parent

Provider-neutral tracker automation CLI and library

What to build

Deliver native and fallback blocking relationships plus deterministic frontier queries. An AI agent can connect a child ticket to its blockers and discover the first open, unblocked, unassigned child of a map.

Acceptance criteria

  • Native blocking dependencies are created where the provider supports them.
  • Blocked by body conventions or equivalent fallback metadata are used when native dependencies are unavailable.
  • The frontier query scopes results to a map's children.
  • Closed blockers are ignored, open blockers exclude a ticket, and assigned tickets are excluded.
  • Frontier ordering is deterministic and follows map order.
  • Provider-specific dependency identifiers and API parameters stay inside adapters.
  • Tests cover native dependencies, fallback dependencies, multiple blockers, closed blockers, assignments, and ordering.

Blocked by

Part of [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## Parent [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## What to build Deliver native and fallback blocking relationships plus deterministic frontier queries. An AI agent can connect a child ticket to its blockers and discover the first open, unblocked, unassigned child of a map. ## Acceptance criteria - [ ] Native blocking dependencies are created where the provider supports them. - [ ] Blocked by body conventions or equivalent fallback metadata are used when native dependencies are unavailable. - [ ] The frontier query scopes results to a map's children. - [ ] Closed blockers are ignored, open blockers exclude a ticket, and assigned tickets are excluded. - [ ] Frontier ordering is deterministic and follows map order. - [ ] Provider-specific dependency identifiers and API parameters stay inside adapters. - [ ] Tests cover native dependencies, fallback dependencies, multiple blockers, closed blockers, assignments, and ordering. ## Blocked by - [Implement wayfinding maps and child tickets](http://gitea.sagacity.ca/steve/skills/issues/21)
steve added the ready-for-agent label 2026-08-17 22:01:08 -04:00
steve added a new dependency 2026-08-17 22:02:10 -04:00
#21 Implement wayfinding maps and child tickets
steve added a new dependency 2026-08-17 22:02:10 -04:00
#23 Implement claim and resolution workflows
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
in-progress
in-review
needs-info
needs-review
Waiting for review by a human
 needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
Wayfinder human decision ticket
 wayfinder:map
Wayfinder decision map
 wontfix
No labels ready-for-agent
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
steve (Steve Beaulac)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#23 Implement claim and resolution workflows
steve/skills
Depends on
#21 Implement wayfinding maps and child tickets
steve/skills
Reference: steve/skills#22