nishantsrivastava81/solution-harness
Copilot agents and skills for planning, building, evaluating, and reviewing solutions, with guided GitHub and Jira workflows
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 documented module boundaries, cross-cutting concerns, and applicable SaaS tenant isolation, observability, and billing boundaries.
Guide one approved feature in a GitHub Copilot cloud task, with real checks and independent evaluation before completion.
Dispatch approved independent stories to GitHub Copilot cloud tasks with gh, then independently review exact PR commits and integrate serially.
Design a feature before building it, including APIs, data models, UI, SaaS tenancy, observability, and usage metering when relevant. Produce a technical design after /add-features and before implementation.
Evaluate features against acceptance criteria and applicable SaaS isolation, security, usage, and operational evidence; mark 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.
Design, implement, and review frontend UI/UX for pages, dashboards, forms, navigation, and components. Use for user-interface work, visual design, responsive layouts, accessibility, interaction states, and browser validation. Brought to you by solution-harness.
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.
Coordinate an approved Jira story subset across local workspaces and GitHub cloud tasks with independent review and manual serial integration.
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.
Read a selected Jira sprint or approved export, reconcile Source IDs and dependencies, and propose a manual hybrid execution plan.
Publish independently accepted delivery evidence or explicitly approved Jira transitions using an authorized Jira integration.
Record a progress log entry for the current session. Appends to docs/PROGRESS.md and updates docs/FEATURES.json if any feature status changed.
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.
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.
Coordinate approved local stories in separate worktrees with manual ownership checks, independent review, and serial integration.
Plan approved story batches, dependencies, ownership, and verification for guided local or GitHub cloud work. Does not launch workers.
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).
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.
Show a dashboard of project status — features complete, in-progress, blocked, with recent activity from the progress log.
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.
Write and run project tests, including tenant isolation, authorization, metering, telemetry privacy, and resilience when applicable.