Agile

The Agile family brings Scrum and Kanban workflows to GitHub Copilot. It is intentionally small — four agents, one clean workflow — and is the recommended starting point for teams new to ubFlow.

ubflow-installer install agile <target-path>

Who is this for?

Teams that develop software using agile methods (Scrum, Kanban, SAFe) and want GitHub Copilot to actively support the full sprint cycle: from writing user stories through implementation to tested, working code.

The Workflow

        flowchart LR
   user(Developer)
   orch(Orchestrator)
   story(Story Author)
   dev(Developer Agent)
   tester(Tester)

   user -- describes feature --> orch
   orch -- needs story --> story
   orch -- needs code --> dev
   orch -- needs tests --> tester
   story -. user story + AC .-> dev
   dev -. implementation .-> tester
    

Agents at a Glance

Agent	What it does
Orchestrator	Understands the developer’s intent and routes to the right specialist. Ideal first contact — just describe what you want to build.
Story Author	Turns a rough feature idea into a well-formed user story with acceptance criteria. Follows the As a … I want … so that … format and checks for completeness and testability.
Developer	Generates clean implementation code that satisfies the acceptance criteria of a user story. Links every code artifact back to its source story for full traceability.
Tester	Derives test cases from acceptance criteria and generates the corresponding test code. Covers both what to verify and how to automate the verification.

Good to know

• Status: draft — agents are being authored; not yet production-ready.

• Scope: Agile SW development only. For safety-critical or ASPICE-regulated projects, see the ASPICE family.

• Extensibility: The four-agent structure is a deliberate starting point. Test case authoring and test code generation can be split into dedicated agents as the family matures.