ultanio/cobot

Fork 4

Epic: Development Workflow & Sub-Agent Automation #53

New issue

Open

opened 2026-02-22 07:57:14 +00:00 by doxios · 1 comment

doxios commented

2026-02-22 07:57:14 +00:00

Collaborator

Overview

Establish a structured development workflow for Cobot where AI sub-agents handle implementation, review, and QA — while humans (Product Owner) maintain control over requirements and merges.

Parent discussion: #52

Stories

Phase 1: Foundation

Story 1: Verify repo labels — Confirm Kind/Epic and Kind/Story labels exist ✅
- AC: Labels exist with correct colors
- Status: DONE
Story 2: Align sub-agent templates — Update templates to match workflow personas
- AC: Templates for cobot-dev, cobot-review, cobot-qa in workspace
- AC: Each template matches the persona definition
- AC: Templates use consistent ROLE/CONTEXT/TASK/OUTPUT/CONSTRAINTS structure
- Estimate: 1 hour

Phase 2: Integration

Story 3: Add dispatcher workflow — Create issue-dispatcher that routes to correct persona
- AC: Dispatcher analyzes issue/PR type
- AC: Routes to: feature-designer (vague) → plugin-reviewer (proposal) → cobot-dev (story)
- AC: Can auto-spawn or recommend
- Estimate: 1 hour
Story 4: Test end-to-end flow — Run one real story through the full workflow
- AC: Story picked from backlog
- AC: cobot-dev implements → cobot-review reviews → cobot-qa verifies
- AC: Human merges
- Estimate: 2 hours

Phase 3: Documentation

Story 5: Document the workflow — Add workflow guide to docs/
- AC: Clear explanation of personas and responsibilities
- AC: How to create epics and stories
- AC: How sub-agents are triggered
- Estimate: 1 hour
Story 6: Retrospective — Document lessons learned
- AC: What worked, what didn't
- AC: Template adjustments captured
- Estimate: 30 min

Personas

Persona	Who	Responsibility
Product Owner	k9ert	Creates epics, approves stories, merges PRs
Architect	Nazim / Zeus	Breaks epics into stories, coordinates
Implementer	sub-agent `cobot-dev`	Code + tests + PR
Reviewer	sub-agent `cobot-review`	Reviews against AC
QA	sub-agent `cobot-qa`	Runs tests, verifies AC
Dispatcher	sub-agent `issue-dispatcher`	Routes issues to correct workflow

Success Criteria

Sub-agent templates aligned with workflow personas
Dispatcher can route issues correctly
At least one story implemented end-to-end via sub-agents
Workflow documented for future use

Dependencies

PR #42 (scheduled execution) — provides subagent spawning infrastructure
Sub-agent skill in workspace — provides template system

## Overview Establish a structured development workflow for Cobot where AI sub-agents handle implementation, review, and QA — while humans (Product Owner) maintain control over requirements and merges. **Parent discussion:** #52 --- ## Stories ### Phase 1: Foundation - [ ] **Story 1: Verify repo labels** — Confirm `Kind/Epic` and `Kind/Story` labels exist ✅ - AC: Labels exist with correct colors - Status: DONE - [ ] **Story 2: Align sub-agent templates** — Update templates to match workflow personas - AC: Templates for `cobot-dev`, `cobot-review`, `cobot-qa` in workspace - AC: Each template matches the persona definition - AC: Templates use consistent ROLE/CONTEXT/TASK/OUTPUT/CONSTRAINTS structure - Estimate: 1 hour ### Phase 2: Integration - [ ] **Story 3: Add dispatcher workflow** — Create `issue-dispatcher` that routes to correct persona - AC: Dispatcher analyzes issue/PR type - AC: Routes to: feature-designer (vague) → plugin-reviewer (proposal) → cobot-dev (story) - AC: Can auto-spawn or recommend - Estimate: 1 hour - [ ] **Story 4: Test end-to-end flow** — Run one real story through the full workflow - AC: Story picked from backlog - AC: cobot-dev implements → cobot-review reviews → cobot-qa verifies - AC: Human merges - Estimate: 2 hours ### Phase 3: Documentation - [ ] **Story 5: Document the workflow** — Add workflow guide to docs/ - AC: Clear explanation of personas and responsibilities - AC: How to create epics and stories - AC: How sub-agents are triggered - Estimate: 1 hour - [ ] **Story 6: Retrospective** — Document lessons learned - AC: What worked, what didn't - AC: Template adjustments captured - Estimate: 30 min --- ## Personas | Persona | Who | Responsibility | |---------|-----|----------------| | **Product Owner** | k9ert | Creates epics, approves stories, merges PRs | | **Architect** | Nazim / Zeus | Breaks epics into stories, coordinates | | **Implementer** | sub-agent `cobot-dev` | Code + tests + PR | | **Reviewer** | sub-agent `cobot-review` | Reviews against AC | | **QA** | sub-agent `cobot-qa` | Runs tests, verifies AC | | **Dispatcher** | sub-agent `issue-dispatcher` | Routes issues to correct workflow | --- ## Success Criteria 1. Sub-agent templates aligned with workflow personas 2. Dispatcher can route issues correctly 3. At least one story implemented end-to-end via sub-agents 4. Workflow documented for future use --- ## Dependencies - PR #42 (scheduled execution) — provides subagent spawning infrastructure - Sub-agent skill in workspace — provides template system

doxios referenced this issue

2026-02-22 07:57:21 +00:00

Define development workflow: personas, ticket lifecycle, and sub-agent templates #52

doxios added the

Kind/Epic

label

2026-02-22 08:05:32 +00:00

doxios commented

2026-02-22 08:06:15 +00:00

Author

Collaborator

Adaptation Plan: Current Sub-Agent System → New Workflow

Current State

My sub-agent templates in skills/sub-agents/references/templates.md:

Template	Purpose
`plugin-reviewer`	Reviews plugin design proposals
`feature-designer`	Designs features from vague requests
`plugin-developer`	Implements code, creates PRs
`pr-reviewer`	Reviews PR code quality
`issue-dispatcher`	Routes issues to workflows

Target State (Workflow Personas)

Persona	Template Name	Purpose
Implementer	`cobot-dev`	Implements stories → branch → code → tests → PR
Reviewer	`cobot-review`	Reviews PR against story AC
QA	`cobot-qa`	Runs tests, verifies AC
Dispatcher	`issue-dispatcher`	Routes issues to correct persona

Gap Analysis

Gap	Action
No `cobot-qa` template	CREATE — test runner + AC verification
`plugin-developer` → `cobot-dev`	RENAME + REFOCUS — story-centric, AC-driven
`pr-reviewer` → `cobot-review`	RENAME + REFOCUS — review against story AC
Dispatcher doesn't know story/epic	UPDATE — add story detection
Templates don't reference AC	UPDATE ALL — AC as first-class input

Implementation Steps

Create cobot-qa template — test runner + AC verification
Refactor plugin-developer → cobot-dev — story-centric with AC
Refactor pr-reviewer → cobot-review — review against story AC
Update issue-dispatcher — detect Kind/Story, Kind/Epic labels
Keep feature-designer and plugin-reviewer — handle unstructured → structured

Workflow Chain

Unstructured Ticket → feature-designer → Epic
Epic → Architect → Stories
Story → cobot-dev → PR → cobot-review → cobot-qa → merge

Next Action

I will update my templates now. ETA: 30 minutes.

## Adaptation Plan: Current Sub-Agent System → New Workflow ### Current State My sub-agent templates in `skills/sub-agents/references/templates.md`: | Template | Purpose | |----------|--------| | `plugin-reviewer` | Reviews plugin design proposals | | `feature-designer` | Designs features from vague requests | | `plugin-developer` | Implements code, creates PRs | | `pr-reviewer` | Reviews PR code quality | | `issue-dispatcher` | Routes issues to workflows | ### Target State (Workflow Personas) | Persona | Template Name | Purpose | |---------|--------------|--------| | Implementer | `cobot-dev` | Implements stories → branch → code → tests → PR | | Reviewer | `cobot-review` | Reviews PR against story AC | | QA | `cobot-qa` | Runs tests, verifies AC | | Dispatcher | `issue-dispatcher` | Routes issues to correct persona | ### Gap Analysis | Gap | Action | |-----|--------| | No `cobot-qa` template | CREATE — test runner + AC verification | | `plugin-developer` → `cobot-dev` | RENAME + REFOCUS — story-centric, AC-driven | | `pr-reviewer` → `cobot-review` | RENAME + REFOCUS — review against story AC | | Dispatcher doesn't know story/epic | UPDATE — add story detection | | Templates don't reference AC | UPDATE ALL — AC as first-class input | ### Implementation Steps 1. **Create `cobot-qa` template** — test runner + AC verification 2. **Refactor `plugin-developer` → `cobot-dev`** — story-centric with AC 3. **Refactor `pr-reviewer` → `cobot-review`** — review against story AC 4. **Update `issue-dispatcher`** — detect Kind/Story, Kind/Epic labels 5. **Keep `feature-designer` and `plugin-reviewer`** — handle unstructured → structured ### Workflow Chain ``` Unstructured Ticket → feature-designer → Epic Epic → Architect → Stories Story → cobot-dev → PR → cobot-review → cobot-qa → merge ``` ### Next Action I will update my templates now. ETA: 30 minutes.

nazim referenced this issue

2026-02-23 11:10:46 +00:00

Code Intelligence Plugin — integrate code-index-mcp for codebase understanding #85

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ultanio/cobot#53

No description provided.

Rows
Columns