analyzer
01DangQuangSE/team-development-skills
Agent Codex
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
DangQuangSE/team-development-skills
Agent Codex
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
DangQuangSE/team-development-skills
Agent Codex
Compare two outputs WITHOUT knowing which skill produced them.
DangQuangSE/team-development-skills
Agent Codex
Evaluate expectations against an execution transcript and outputs.
DangQuangSE/team-development-skills
Agent Claude Code
Generic code review agent. Reads CLAUDE.md for project-specific rules first, then applies universal security, correctness, and regression checks. Use immediately after writing or modifying code. Does not re-score architecture/maintainability — that is ck:quality's job; if a ck:quality report already exists for the…
DangQuangSE/team-development-skills
Agent Claude Code
Root cause analysis agent. Used by /fix (receives scout evidence report) and /cook (receives tester failure output). Forms hypotheses, confirms/rejects against codebase, applies a minimal fix, and reports findings.
DangQuangSE/team-development-skills
Agent Claude Code
Finalize sub-agent used by /cook and /fix. Identifies which docs were affected by the implementation and updates them minimally to reflect the new state.
DangQuangSE/team-development-skills
Agent Claude Code
Finalize sub-agent used by /cook and /fix. Stages changed files, creates conventional commits, and asks the user whether to push. Never force-pushes or skips hooks.
DangQuangSE/team-development-skills
Agent Claude Code
Red-team reviewer for the /plan pipeline. Reads plan.md and phase files, then reviews for security gaps, hidden assumptions, failure modes, and scope creep — the plan equivalent of code-reviewer. Returns structured findings with ACCEPTED/NOTED verdicts.
DangQuangSE/team-development-skills
Agent Claude Code
Plan-creation sub-agent for the /plan pipeline. Given a feature description and optional research reports, writes the full plan directory: plan.md overview + one phase-XX-{name}.md per phase. Used in Fast, Hard, Parallel, and Two modes.
DangQuangSE/team-development-skills
Agent Claude Code
General-purpose Playwright screenshot agent. Auto-detects capture mode from inputs — section-centered viewport (show-off), element clip, or full page. Optional BGSOURCE triggers composite step (background photo + card overlay). Spawned by /show-off and any task needing screenshots.
DangQuangSE/team-development-skills
Agent Claude Code
Finalize sub-agent used by /cook and /fix. Syncs completed phase checkboxes in plan.md, updates plan Status, and reports overall progress. Skipped gracefully if no plan.md exists.
DangQuangSE/team-development-skills
Agent Claude Code
Independent senior-engineering quality auditor for the ck:quality skill. Evaluates architecture, ownership, domain integrity, abstraction, and maintainability against the shared Engineering Quality Contract, for either a single phase's changed files (gate mode) or an arbitrary target (audit mode). Never edits files…
DangQuangSE/team-development-skills
Agent Claude Code
General-purpose research sub-agent. Given a topic and an assigned role, investigates one angle and returns a structured report. Spawned in parallel pairs (Primary + Alternative) by any pipeline needing option comparison. Budget ≤5 tool calls.
DangQuangSE/team-development-skills
Agent Claude Code
Evidence-gathering agent for the /fix pipeline. Given a bug description, greps for error patterns, reads affected source files, and checks recent git changes. Returns a structured evidence report within a ≤6 tool call budget.
DangQuangSE/team-development-skills
Agent Claude Code
Testing sub-agent for the ck:test skill. Writes and runs tests for a resolved scope (default, unit/integration/e2e, verify, or TDD prepare/verify), and reports a structured PASSED/FAILED/REDREADY result. Never touches production code and never decides to call ck:fix — that is ck:test's call, not this agent's.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: