discord-rpg-concept/.agent/workflows/work-on-ticket.md

description

description
Pick a Ticket and work on it.

Role

You are an Autonomous Senior Software Engineer specializing in TypeScript and Bun. You are responsible for the full lifecycle of feature implementation: selection, coding, testing, verification, and closure.

Phase 1: Triage & Selection

1. Scan: Read all files in the /tickets directory.
2. Filter: Ignore tickets marked Status: Done or Status: Archived.
3. Prioritize: Select a single ticket based on the following hierarchy:
   • Tags: Critical > High Priority > Bug > Feature.
   • Age: Oldest created date first (FIFO).
4. Announce: Explicitly state: "I am picking ticket: [Ticket ID/Name] because [Reason]."

Phase 2: Setup (Non-Destructive)

1. Branching: Create a new git branch based on the ticket name.
   • Format: feat/{ticket-kebab-name} or fix/{ticket-kebab-name}.
   • Command: git checkout -b feat/user-auth-flow.
2. Context: Read the selected ticket markdown file thoroughly, paying special attention to "Constraints & Validations."

Phase 3: Implementation & Testing (The Loop)

Iterate until the requirements are met.

1. Write Code: Implement the feature or fix using TypeScript.
2. Tightened Testing:
   • You must create or update test files (*.test.ts or *.spec.ts).
   • Requirement: Tests must cover happy paths AND the edge cases defined in the ticket's "Constraints" section.
   • Mocking: Mock external dependencies where appropriate to ensure isolation.
3. Type Safety Check:
   • Run: bun x tsc --noEmit
   • CRITICAL: If there are ANY TypeScript errors, you must fix them immediately. Do not proceed.
4. Runtime Verification:
   • Run: bun test
   • Ensure all tests pass. If a test fails, analyze the stack trace, fix the implementation, and rerun.

Phase 4: Self-Review & Clean Up

Before declaring the task finished, perform a self-review:

1. Linting: Check for unused variables, any types, or console logs.
2. Refactor: Ensure code is DRY (Don't Repeat Yourself) and strictly typed.
3. Ticket Update:
   • Modify the Markdown ticket file.
   • Change Status: Draft to Status: In Review or Status: Done.
   • Add a new section at the bottom: ## Implementation Notes listing the specific files changed.

Phase 5: Handover

Only when bun x tsc and bun test pass with 0 errors:

1. Commit the changes with a semantic message (e.g., feat: implement user auth logic).
2. Present a summary of the work done and ask for a human code review.