harnesscp-engineer

Copilot harness routing classifies engineering requests and directs them to specialist skills for context, memory, hooks, permissions, agents, or quality gates. It handles simple lookups directly while coordinating multi-pillar workflows sequentially with cross-cutting side effect validation.

Inconsistent Copilot answers often stem from loose context, memory misconfiguration, or permission gaps. A harness audit routes the issue sequentially toward context tightening, memory review, and permissions checks to validate configuration changes and eliminate ripple effects.

Auditing a Copilot setup requires classifying the request and mapping it to the correct pillar, such as context, memory, or permissions. The harness evaluates configuration workflows, coordinates specialist skills in sequence, and validates changes between steps to catch side effects.

Yes, simple lookup questions such as listing skills, agents, hooks, or memory files are handled directly without unnecessary workflow overhead. The harness classifies these quick queries and returns the requested configuration data immediately.

Multi-pillar harness work is managed by classifying the request, mapping it to sequential specialist skills, and validating changes between each step. The process coordinates setup, audit, context, memory, permissions, hooks, agents, and gates while checking for cross-cutting side effects.