agent-ix/dev-team
Team planning, leadership, coding, review coordination, feature feedback, and program status workflows.
Run a ticket's coding stage as the dedicated coder role. Work in one assigned worktree, follow the repo's own conventions, run the cheap checks first, then the gate once on the final head, open the PR, freeze it, and report. Later fix rounds fix every review finding inside the same PR. Use when invoked as /coder, or when dispatched as the coder subagent for a ticket (for example from /team-leader).
Run an acceptance check on a delivered feature against its ticket's acceptance criteria and return a per-criterion PASS/FAIL verdict with evidence. Use when a feature is claimed done, before closing its ticket, or when asked to accept, verify or UAT a feature. For open-ended experience feedback use feature-feedback.
Give structured works / friction / gaps feedback on a feature you have just used, as a stakeholder or UAT tester. Use after trying a script, tool, skill or workflow, or when asked to test something and report back. To request something new use feature-request; for a pass/fail acceptance verdict use feature-check.
Write a request for a new capability as a Linear ticket that another agent can build and a stakeholder agent can later accept. Use when you hit something the tooling cannot do, want new functionality, or are asked to file a feature request. For feedback on an existing feature use feature-feedback; to verify a delivered feature use feature-check.
Run a PR's review stage as the dedicated reviewer role — run every applicable review method (code-review, rust-review, quoin gap-analysis, quoin spec-review and its sub-analyses) in one pass, let each write its own quire-validated SpecReview artifact, and post findings and later dispositions to the project's ticket tracker (Linear by default) with machine-readable markers so review data survives outside chat and each comment can be mined on its own, with no git join needed. Use when invoked as /reviewer, when dispatched as the reviewer subagent for a PR (for example from /team-leader), or when a review needs to be logged to the tracker instead of only the PR.
Report evidence-backed status for a Linear initiative, project, or multi-repository program, including completed work, blockers, architecture and quality concerns, and the next owned action.
Run a team as its long-lived team leader. Pull work from the team's tracker plan (initiatives, projects, epics) in order, dispatch spec authors, coders and reviewers as subagents in fresh contexts, fix every finding inside the original PR, verify and merge reviewed work, keep tracker state true, and keep the lane landing for hours or days without waiting on the owner. Use when invoked as /team-leader <team or project> or told "you are team leader for X" / "you are MAIN TEAM".
Turn an idea or change request into a structured Linear program, project, and ready tickets with dependencies, specification and architecture gates, then hand execution to a team leader or coder. Also review an existing team focus.