Set up a Planner-Generator-Evaluator agent harness for feature development.
npx skills add https://github.com/Derek-X-Wang/skills --skill feat-harness
Please help me install this Agent Skill. Skill: feat-harness Source: https://github.com/Derek-X-Wang/skills/tree/main/feat-harness Command: npx skills add https://github.com/Derek-X-Wang/skills --skill feat-harness
Provides a product-level orchestration pattern that coordinates four specialized agents (Planner, Generator, Evaluator, and Auditor) to plan, build, evaluate, and audit features with clear traceability and reusable templates.
<project>/.claude/harness/, including templates from references/agents/ and references/criteria/.Bootstrapping a harness creates the project-specific harness directory and agent configurations so you can begin feature work immediately.
High-intent search queries and answers about installing and using this skill.
Multi-agent orchestration for feature development is handled by a Planner-Generator-Evaluator harness that coordinates specialized agents via file-based communication to preserve an audit trail and enable iterative improvement.
A planner-generator-evaluator agent harness is used to orchestrate feature development by assigning structured roles for spec planning, implementation, evaluation, and optional auditing with clear traceability and reusable templates.
To set up a multi-agent harness, bootstrap the project-specific configuration which writes agent configs and evaluation criteria into the project's .claude/harness directory using templates loaded from references.
File-based communication between autonomous agents is supported to preserve an audit trail, allowing team members to review outputs and audit history throughout the iterative feature development workflow.
Iterative feedback loops for feature implementation are supported by the Evaluator and optional Auditor agents, which apply loaded evaluation criteria and rubrics to surface specs and feedback through a standardized directory structure.
Limitations include the requirement to bootstrap project-specific configs into a dedicated harness directory and reliance on file-based communication, which may introduce overhead for smaller projects not needing full audit traceability.
zxdxjtuAnalyze repository files and team norms to generate .harness configuration artifacts.
larus-peritusTranslates task specifications into implementation guidance for apps/.
richardnpaulCoordinates Planner, Generator, and Evaluator agents to iteratively build and test software.
statsclawEnforce an append-only shared mailbox for standardized agent team communication.