Automate ChordLens implementation from a plan using TDD or type-first cycles.
npx skills add https://github.com/xmun74/chordlens --skill chordlens-implement
Please help me install this Agent Skill. Skill: chordlens-implement Source: https://github.com/xmun74/chordlens/tree/main/.claude/skills/chordlens-implement Command: npx skills add https://github.com/xmun74/chordlens --skill chordlens-implement
chordlens-implement automates the implementation phase of ChordLens based on the project plan located at _workspace/02_plan.md and orchestrates validation via code critique, enabling independent verification and structured progress.
Run the chordlens-implement skill to start the plan-based development phase and trigger the appropriate cycle with code critique.
High-intent search queries and answers about installing and using this skill.
Plan-driven implementation starts from the _workspace/02_plan.md file and automates the development phase. It drives FE/BE development, testing, and review while ensuring phase transitions and output artifacts are traceable for code-critique review.
Vitest integration detects availability and applies a TDD cycle guiding RED→GREEN→REFACTOR. If Vitest is not installed, it defaults to a type-first cycle guiding TYPE→IMPL→VERIFY workflows instead, ensuring validation without interrupting development.
No, Vitest is not required. The workflow detects Vitest availability and selects a type-first cycle guiding TYPE→IMPL→VERIFY sequences when it is absent, ensuring structured implementation validation regardless of testing framework presence.
Code critique integration produces _workspace-based critique documents for continuous improvement and governance. Phase 3 critiques implementation while Phase 4 finalizes and archives outputs including code changes and critique artifacts for review.
Team coordination supports FE/developer, BE/developer, and code-critic collaboration with clear task flow and checkpoints. Phase-based workflow manages environment checks, implementation, critique, and finalization across all roles.
Without Vitest, the workflow substitutes TDD with a type-first cycle using TYPE→IMPL→VERIFY sequences. This lacks runtime test validation but maintains structured progress, type safety, and traceable artifacts for code-critique review.
botPhUConfigure and optimize Vitest for Vite-based projects, including Jest migration.
npc-chrisAutomate code deployment by merging, testing, reviewing, and pushing changes.
Lev-itEnforce Red-Green-Refactor TDD cycles for TypeScript/Node.js projects.
cmb-syOrchestrate a TDD workflow from feature spec to merge-ready code.
