solution-harness-plugin

Run a goal-bounded autonomous loop over the harness — select, build, verify, and commit features one at a time with a maker/checker split, an explicit stop-contract, and a per-run token/commit budget. Best run in the orchestrator agent.

Sync FEATURES.json and PLAN.md after architecture or scope changes mid-project. Preserves completed feature status while updating not-started features to align with the latest ARCHITECTURE.md and PLAN.md.

Initialize a new harness-managed solution project from a brief idea. Use when starting a brand new project. Creates docs/IDEA.md, docs/PLAN.md, docs/FEATURES.json, docs/ARCHITECTURE.md, docs/PROGRESS.md, AGENTS.md, and .github/copilot-instructions.md.

Design a feature before building it — research latest patterns, evaluate approaches, design APIs/data models/UI, and produce a technical design document. Use after /add-features and before the builder starts implementing.

Provide feedback on a design document and request changes. Use after /design-feature to iterate on the technical design before implementation begins. Supports multiple rounds of review.

Plan new features to add to an existing onboarded project. Analyzes impact on existing modules, designs features that fit the current architecture, and ensures backward compatibility.

Verify that the codebase follows the documented architecture. Checks for module boundary violations, circular dependencies, and cross-cutting concern leaks.

Run quality evaluation on the current solution. Grades every completed feature against acceptance criteria on Completeness, Correctness, Code Quality, Test Coverage, and Architecture Fit. Marks failures as needs-rework.

Diagnose and fix a bug in the existing codebase. Enforces: reproduce first, write failing test, implement smallest fix, verify all tests pass, document root cause.

Assess whether the harness components are still appropriate for the current model and project. Audits each component for relevance, checks evaluator accuracy, measures feature velocity, and recommends simplifications.

Record a progress log entry for the current session. Appends to docs/PROGRESS.md and updates docs/FEATURES.json if any feature status changed.

Show the next feature, refactoring task, or bug fix to work on from the plan. Reads docs/FEATURES.json and docs/PROGRESS.md to determine what to build next.

Onboard an existing codebase into the harness. Analyzes the project, documents architecture, catalogs existing features, and creates all harness state files. Use when you want to apply the harness to a project that already has code.

Run quality validation checks before committing. Tests pass, no hardcoded secrets, imports resolve, FEATURES.json consistency, progress logged. Use before every git commit.

Plan refactoring tasks for an existing project with risk assessment and rollback plans. Categories: structural, quality, performance, test, dependency, security. Orders tasks by risk (low first).

Show a dashboard of project status — features complete, in-progress, blocked, with recent activity from the progress log.

Run and verify tests for the current project. Provides patterns for writing good tests, detecting project type, and running appropriate test suites.