Agent Skills: ca-implement-plan
Build a saved task-by-task implementation plan in an isolated worktree, milestone by milestone, with Claude checkpoint reviews between milestones and Claude-reviewed final rounds gating the PR before it is marked ready — the Codex half of the ca (Cooperate Agents) loop. Use when the user points at a plan file under docs/ca/plans or any task-by-task plan and says things like "implement this plan", "build the plan at this path", "run the ca loop on this plan", or "have Claude review what you built". Human confirmation is required at key decision points and before cleanup.
ID: ken2403/.claude-paralell-dev-plugin/ca-implement-plan
3
Install this agent skill to your local
Skill Files
The files that make up ca-implement-plan.
More agent skills
- generate-frontend-formsGuide for creating forms using Sentry's new form system. Use when implementing forms, form fields, validation, or auto-save functionality.
- ralph-loopRun, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
- webapp-testingWeb application testing principles. E2E, Playwright, deep audit strategies.
- designing-testsDesigns and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
- intelligent-routingAutomatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
- building-product-empty-statesGuide for adding a product setup empty state — the skippable first-run screen a product scene shows until real data arrives, built on the shared ProductEmptyState component. Use when adding an empty state or first-run/setup screen to a product scene, declaring `emptyState` on a `SceneExport`, writing a product setup-status detection logic, building an animated example-data preview widget, or deciding between the scene-level `ProductEmptyState` gate and an inline `ProductIntroduction` panel. Covers the `productSetupStatusLogic` single-layer contract, real-data detection rules, local-only skip semantics, wizard commands, and design tokens.