Aiteamkit — Testing skill for Claude Code

AI Team Kit (`atk`)

Twenty-five skills covering the software delivery lifecycle of a **company project team**. Every skill assumes work has an author and a separate reviewer, decisions have an owner, and artifacts are read by someone who was not in the conversation that produced them. Those are roles rather than a headcount: a solo developer holding all of them gets the same gates, and still gives each approval themselves.

Compatible with Claude Code, Cursor, and OpenAI Codex CLI.

Walkthrough of what each skill means and when to use it: [docs/skills-overview.md](docs/skills-overview.md) (English) / [docs/vi/skills-overview.md](docs/vi/skills-overview.md) (Tiếng Việt).

Lifecycle

flowchart TD
    subgraph L0["0. Setup"]
        direction LR
        I["init"] --> T["tailor"]
    end
    subgraph L1["1-2. Requirement and estimate"]
        direction LR
        IN["intake"] --> C["catchup"] --> E["estimate"]
    end
    subgraph L2["3-4. Design, split, sequence"]
        direction LR
        D["design-doc"] --> SP["spec"] --> B["breakdown"] --> CV["convention"] --> P["plan"]
    end
    subgraph L3["5-6. Build and test"]
        direction LR
        IM["implement"] --> V["verify"] --> R["review"] --> Q["qa"] --> RC["run-cases"]
        R -.->|Blocking findings| IM
    end
    subgraph L4["7-8. Release, operate, learn"]
        direction LR
        RL["release"] --> IC["incident"] --> RT["retro"]
    end
    L0 --> L1 --> L2 --> L3 --> L4
    L4 -.-> NC["Next cycle
starts again at intake"]

Four skills answer an event rather than a phase: `fix` when a defect is reported, at any point; `security` on a schedule, or before or after a release; `onboard` when someone joins; `handover` when someone leaves or a phase ends. `help` answers a question instead: which of the others to run, read from the state of the project. `orchestrate` carries several pieces of work through the phases at once, running the others as jobs once a person app