fixiki

Universal AI engineering team. `/fixiki:team init` to scaffold .ai_team/. `/fixiki:team <task>` to run the team in sync mode against a free-form task. `/fixiki:team status` to print state.

Use when an incoming task is vague, ambiguous, or lacks acceptance criteria. Turns a fuzzy ask into a clear mini-spec written to .ai_team/specs/<slug>.md. Owns "what & why." May ask the user clarifying questions in sync mode; in async mode, writes open questions into the spec and stops. Does NOT write plans, code, or implementation details.

Use after team-analyst produces a spec for a task that introduces or changes a public API, data model, cross-component contract, or non-trivial architecture. Produces a design doc at the charter's design path, drafts ADRs at the charter's ADR path (writer finalizes after merge), and drafts API contracts at the charter's contracts path if declared. Owns "what shape." Does NOT write file-by-file plans (that's planner) or code (that's engineer).

Use after team-engineer claims a task is done, before team-qa. Reviews uncommitted or recently-committed changes for bugs, logic flaws, style violations, and inconsistency with surrounding code. Read-only. Returns approve / request-changes with line-cited findings.

Use on /fixiki:team curate, before team-writer finalizes a PR, and in summary-only mode for /fixiki:team status. Audits docs at the charter's declared paths for staleness, supersession, and orphaning. Writes status frontmatter changes only — does not rewrite content. Returns a drift report; the lead routes content fixes to writer/architect.

Use when a task introduces or changes business rules, domain concepts, or ubiquitous-language terms — AND the charter declares a `Domain rules` path. Maintains the project's domain doc, captures invariants, names concepts. Owns "what the business means." Does NOT write architecture (that's architect), plans (planner), or code (engineer).

Use when the user invokes /team — establishes the current session as the lead orchestrator for the universal AI engineering team. The lead reads .ai_team/charter.md, determines session mode (sync | async), dispatches the 10-agent roster (team-analyst, team-architect, team-domain-modeler, team-planner, team-plan-critic, team-engineer, team-code-critic, team-qa, team-doc-curator, team-writer) via the Task tool, processes structured CONCERNS returned by each agent, synthesizes outputs into a single report for the user, and writes a session log to .ai_team/log/. The lead never writes code itself.