Development

When a developer is ready to build, Konductro handles the setup: branch creation, context delivery, and status tracking. The developer focuses on code.

Starting Work

Start work from the UI or CLI

Click Start Work on the task detail in the Konductro UI, or run /start-work in Claude Code or Amazon Q.

# In Claude Code
/start-work

Branch auto-created

A feature branch is created automatically on the git provider (Gitea or Azure DevOps), named after the ticket key.

Ticket spec pushed to the repo

A ticket spec file is pushed to the repository at .tickets/TICKET-KEY.md. This file contains everything the developer needs:

Task description and acceptance criteria
Architecture slice relevant to this task
Implementation steps from decomposition
Prior planning decisions that affect this work

Status updates automatically

The task status moves to in_progress. The sprint board updates in real time. No manual status changes needed.

The Ticket Spec File

The ticket spec is the bridge between planning and development. It lives in the repo at .tickets/TICKET-KEY.md and contains a structured markdown document with:

Section	Contents
Overview	Task title, parent story, and description
Acceptance criteria	What must be true when this task is done
Architecture notes	Relevant data models, API contracts, and design decisions
Implementation steps	Ordered steps from decomposition
Files to modify	Specific files to create or change
Context	Links to related tasks, dependencies, and prior decisions

Development with CLI Plugins

During development, the CLI plugins provide tools that keep the developer connected to Konductro:

Tool	Purpose
`get_ticket_context`	Load full task context (AC, notes, parent story, repo, artefacts)
`list_my_tickets`	See all assigned tasks with status, project, sprint, and branch
`start_work`	Start work on a task (creates branch and pushes spec)

The developer writes code, commits, and pushes as normal. When the work is ready for review, they create a pull request.