Tools Reference

The Konductro CLI plugins (@konductro/claude-plugin, @konductro/q-plugin, @konductro/codex-plugin and @konductro/cursor-plugin) expose MCP tools that the AI in your editor calls during a conversation to work with Konductro.

This page describes the published plugins: Claude Code 2.4.0, Amazon Q (Kiro CLI) 2.4.0, OpenAI Codex 2.4.0, Cursor 1.3.0. All four ship the same tools and commands.

Tickets

Tool	What it does	When you would use it
`list_my_tickets`	Lists the tickets assigned to you, with key, title, status, project, phase, sprint and branch.	To see what is on your plate, or find a ticket key before starting work.
`get_ticket_context`	Loads a ticket’s description, acceptance criteria, architectural notes, parent story, repository and approved documents. Accepts a ticket key such as MRB-1.	Before working on a ticket, so the AI has the same context you would read in Konductro.
`start_work`	Creates the ticket’s branch on your git provider, pushes the ticket spec file to the repository and moves the ticket to In Progress.	When you pick up an assigned ticket. The start-ticket command walks you through it.
`append_story_developer_note`	Adds an entry to the parent story’s developer notes. Konductro records the author, time and task.	When you work out something the next person on the same story should know, such as a decision or a gotcha.

Pull requests

Tool	What it does	When you would use it
`create_pr`	Opens a pull request for a ticket on your git provider, assigns a reviewer from the project’s rules and moves the ticket to PR Open.	When the work on a ticket is done, tested and reviewed locally.

Work items

Tool	What it does	When you would use it
`create_work_item`	Creates a story, task or bug in the project the current repository belongs to. Everything created lands in Draft and needs an SDM’s approval.	When you notice missing work while coding and want to log it without opening Konductro.
`update_work_item`	Changes the title, description or acceptance criteria of a work item you own. Nothing else can be changed from here.	To correct a work item you are working on, such as a wrong acceptance criterion.
`delete_work_item`	Deletes a task or bug that has not started. Stories, and bugs filed by QA, cannot be deleted this way.	To remove a task or bug you created by mistake, before anyone has started on it.

Technical analysis

Tool	What it does	When you would use it
`list_tech_analysis_tasks`	Lists the technical analysis assignments waiting for you.	At the start of a technical analysis, to find the one assigned to you.
`get_task_context`	Loads the requirements, project details and repositories for a technical analysis.	Before analysing the codebase, so the analysis answers the approved requirements.
`submit_tech_analysis`	Sends the finished technical analysis document and a summary of the conversation back to Konductro.	When the analysis is complete and ready for review in Konductro.

Decomposition

Tool	What it does	When you would use it
`list_decomposition_tasks`	Lists the stories assigned to you for decomposition.	At the start of a decomposition, to find the story assigned to you.
`get_decomposition_context`	Loads a story’s details, requirements, architecture and repositories.	Before breaking the story into tasks against the real code.
`submit_decomposition_task`	Submits one task for the story being decomposed. Called once per task.	As each task in the breakdown is ready.
`complete_decomposition`	Marks the story’s decomposition as complete once every task has been submitted.	After the last task is submitted.

Developer briefs

Tool	What it does	When you would use it
`submit_regenerated_brief`	Saves a regenerated developer brief as the task’s current brief. Earlier versions stay in the brief history.	When you want a task’s brief rewritten for your AI coding tool and the current code. The regenerate-brief command uses it.

Bugs

Tool	What it does	When you would use it
`get_bug_for_enrichment`	Loads a bug’s description, acceptance criteria, project and existing notes.	When you are triaging a bug and want to investigate it against the code.
`submit_bug_enrichment`	Adds structured technical findings to a bug. The original description is never changed.	After investigating a bug, so whoever fixes it starts from your findings.

Prototypes

Tool	What it does	When you would use it
`find_project_prototypes`	Finds the UX prototypes for the project the current repository belongs to.	When you are building a feature and want the approved prototype to work from.
`list_prototype_tasks`	Lists the prototype builds assigned to you.	At the start of a prototype build.
`get_prototype_context`	Loads the design system, approved documents and preview for a prototype build.	Before building a prototype.
`start_prototype_work`	Marks a prototype build as in progress.	When you start building a prototype.
`request_upload_credentials`	Issues short-lived credentials that can only upload this prototype’s files.	When the prototype is built and ready to publish.
`submit_prototype`	Submits the published prototype and its page list to Konductro.	After every prototype file has been uploaded.

Repository profiling

Tool	What it does	When you would use it
`profile_repository`	Scans the current repository and sends its profile (tech stack, dependencies, APIs) to Konductro.	When a repository is first linked to a project, or after significant changes, so planning works from an accurate picture.

Tool Authentication

All tools authenticate using your personal CLI token, configured during installation. The token is sent with each API request to the Konductro backend. No additional authentication is needed per-tool.