Implement features from Plans.md with tests in a Next.js/TypeScript stack.
npx skills add https://github.com/Chachamaru127/claude-code-harness --skill impl
Please help me install this Agent Skill. Skill: impl Source: https://github.com/Chachamaru127/claude-code-harness/tree/main/skills/impl Command: npx skills add https://github.com/Chachamaru127/claude-code-harness --skill impl
This Skill bridges the gap between planning and execution by automatically writing feature code and comprehensive tests based on tasks defined in Plans.md, drastically reducing manual coding time.
Plans.md, updates task status, and writes the actual code for new features, components, or API endpoints.cc:TODO? The /work command uses this Skill to read the plan, create the React component and backend route, write tests, and update the task status to cc:完了—all automatically.Execute the /work command in Claude Code to automatically pick up the next cc:TODO task from Plans.md and begin implementation.
High-intent search queries and answers about installing and using this skill.
Automated feature implementation reads tasks from `Plans.md`, generates React components, API endpoints, and backend routes, then writes tests and updates task status. Execute the `/work` command to pick up the next `cc:TODO` task and implement it end-to-end with code generation and test creation.
Yes. Intelligent test generation creates unit and integration tests for implemented features, ensuring quality and preventing regressions. Tests are written alongside feature code during the implementation process.
Implementation targets Next.js and TypeScript stacks, handling API endpoints, UI components, utilities, and tests within that environment. LSP-based verification ensures code quality during and after generation.
Task status updates are handled automatically during implementation. Tasks marked as `cc:TODO` in `Plans.md` transition to `cc:完了` upon successful feature completion and test generation.
Yes. The Skill uses memory-enabled past-pattern references to apply existing code conventions and architectural patterns, ensuring new implementations align with your codebase's established style.
Define tasks in `Plans.md` with clear descriptions and mark them as `cc:TODO`. The Skill reads these structured plans and automatically generates corresponding code, components, routes, and tests based on the specifications provided.
carlosmarteOrganize project work into a Feature > Story > Task plan tree as Markdown files.
mwguerraAnalyze codebases to identify production-readiness gaps using Pest and Playwright tests.
timequityGenerate and run tests after each code change with pass/fail reporting.
VidyaBodepudiGuide incremental feature development with test-driven practices and small verifiable steps.