Ticket Lifecycle Workflow

Complete workflow from starting a ticket to delivering work.

Prerequisites

CLI installed and authenticated
Access to JIRA/GitHub workspace

The Standard Flow

# 1. Start ticket
wseng start LAMBDA-12345

# 2. Plan implementation
# Edit .context/plan/plan.md with your approach

# 3. Save plan (transitions ticket to In Progress)
wseng ws save-plan

# 4. Make code changes

# 5. Commit
wseng commit

# 6. Generate changelog
wseng changelog

# 7. Record demo
wseng demo

# 8. Submit for QC (manual)

Step 1: Start the Ticket

wseng start LAMBDA-12345

What this does:

Creates branch and pull request
Downloads ticket description to .context/ticket.md
Auto-generates blank plan at .context/plan/plan.md
Transitions ticket to "Planning" status

Step 2: Write the Plan

Open .context/plan/plan.md and document your implementation approach. Use Cursor or your IDE to explore the codebase and understand requirements from .context/ticket.md.

Good plan structure:

## Files to Create/Modify

- src/services/user.service.ts
- src/resolvers/user.resolver.ts

## Implementation Steps

1. Add getUserProfile method to UserService
2. Expose via GraphQL resolver
3. Add unit tests for service
4. Add E2E test for GraphQL query

Step 3: Save the Plan

wseng ws save-plan

Saves plan to repository and transitions ticket to "In Progress".

Step 4-6: Implement, Commit, Document

Make your changes, then:

# AI-generated commit messages
wseng commit

# Generate summary of changes
wseng changelog

Step 7: Record Demo

wseng demo

Records screen with OBS Studio, uploads to Google Drive, links to ticket/PR. See command reference for OBS setup.

Common Variations

NO-TICKET branches:

wseng start NO-TICKET "quick fix description"

Create new ticket:

wseng start NEW "feature description"

Split into subtasks:

wseng subtask LAMBDA-12345 --type backend --start

Common Pitfalls

❌ Bad: Starting ticket assigned to someone else

wseng start LAMBDA-12345
# Error: Ticket assigned to another engineer

Solution: Use --force-assignment to override.

❌ Bad: Skipping the plan

Starting to code immediately without writing a plan leaves the ticket in "Planning" status and makes story point calculation inaccurate.

Solution: Always write and save your plan before coding. It forces you to think through the approach.