• Gitea Project Details for Role Refactoring

    9 Open
    1 Closed

    Gitea Project Details for Role Refactoring

    Here's the project structure I'd recommend creating in Gitea to track this work:

    Project Configuration

    Project Name: Agent Coordination v2 - Role Refactoring

    Description: Refactoring monolithic gitea_dev into three distinct roles (gitea_coder, gitea_reviewer, gitea_pm) with proper tool boundaries and agent handoff capabilities.

    Project Settings

    • Workflow: Custom (3-column or 4-column)
    • Columns: Backlog, In Progress, In Review, Done
    • Default Assignee: Unassigned (agents will claim based on role)

    Tickets to Create

    Phase 1: Foundation

    Ticket 1: Project Setup and Tool Discovery

    • Description: Create project board, establish tracking, audit current gitea_dev tool inventory
    • Labels: infrastructure, phase-1
    • Estimate: 1

    Ticket 2: Implement gitea_coder Role

    • Description: File CRUD, branch creation, commit messaging, PR creation with scope gating
    • Labels: role-implementation, phase-1
    • Dependencies: Ticket 1

    Ticket 3: Add Scope Enforcement to gitea_coder

    • Description: Enforce branch naming conventions, ticket binding validation, prevent main pushes
    • Labels: security, phase-1
    • Dependencies: Ticket 2

    Phase 2: Review Flow

    Ticket 4: Implement gitea_reviewer Role

    • Description: PR diff analysis, comment on PR, pass/fail review logic
    • Labels: role-implementation, phase-2
    • Dependencies: Ticket 2

    Ticket 5: Add Quality Gates to gitea_reviewer

    • Description: Integrate lint/test results, enforce minimum quality thresholds
    • Labels: quality, phase-2
    • Dependencies: Ticket 4

    Phase 3: PM and Automation

    Ticket 6: Implement gitea_pm Role

    • Description: Merge authority, ticket updates, ticket closure, human escalation path
    • Labels: role-implementation, phase-3
    • Dependencies: Ticket 4

    Ticket 7: Create Agent Handoff System

    • Description: Owui_chat tool, signal emission between roles, state transition automation
    • Labels: automation, phase-3
    • Dependencies: Tickets 2, 4, 6

    Ticket 8: Create k8s/cron Triggers

    • Description: Kickoff agents based on ticket state changes
    • Labels: infrastructure, phase-3
    • Dependencies: Ticket 7

    Phase 4: Cleanup

    Ticket 9: Deprecate gitea_dev

    • Description: Remove monolithic endpoint, validate all three new roles working
    • Labels: cleanup, phase-4
    • Dependencies: Tickets 3, 5, 6

    Validation Checkpoint

    Ticket 10: Manual Workflow Validation

    • Description: Execute complete manual workflow for each role before automation
    • Labels: validation, gate
    • Dependencies: Tickets 3, 5, 6

    Priority Order for Creation

    Create these tickets in order (1 → 10), which respects the dependencies. Ticket 10 should be created last and serves as your pre-automation gate.

    Want me to generate these as a structured format you can paste directly into Gitea, or would you prefer I create them directly using the gitea tools?