scaffold-dashboard-system-wiring

Enforce working scope and review mandates for dashboard tasks in Docker.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill scaffold-dashboard-system-wiring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-dashboard-system-wiring
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/scaffold-dashboard-system-wiring
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill scaffold-dashboard-system-wiring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent resolution table, working-scope declaration, and review mandates for the scaffold-dashboard orchestrator running inside a Docker container against the dashboard/ subtree of ue-claude-scaffold.

Core Features & Use Cases

  • Working scope enforcement for the dashboard subtree and explicit owner declarations for cross-scope work.
  • Clear agent-role mandates and resolvable delegation prompts to ensure safe, auditable orchestration.
  • Review-tag override guidance and scoped task tracking to prevent cross-contamination between tracks.

Quick Start

Define a dashboard task, declare its scope, and run the scaffold-dashboard orchestrator to execute it end-to-end.

Frequently Asked Questions about scaffold-dashboard-system-wiring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce working scope on dashboard tasks in a Docker container?

To enforce working scope on dashboard tasks, codify an agent-resolution table and mandate a 'Working scope' line in delegation prompts. This constrains the orchestrator to the dashboard/ subtree and requires explicit owner declaration for any cross-scope work.

What is a review mandate for scoped agent orchestration?

A review mandate is a defined rule enforcing agent roles, scope lines, and tag overrides during task reviews. It ensures safe, auditable changes by preventing cross-contamination between tracks when an orchestrator runs against a constrained subtree.

How do I prevent cross-contamination between orchestration tracks?

Prevent cross-contamination by implementing defined track scope, scoped task tracking, and review-tag override guidance. Explicit owner declarations are required for any work crossing into non-dashboard areas.

Does the scaffold-dashboard orchestrator require a Docker container?

The scaffold-dashboard orchestrator runs inside a Docker container against the dashboard/ subtree. This isolated execution environment is required to safely apply agent roles and enforce the working scope declarations.

What's the best way to declare cross-scope work in dashboard orchestration?

The best way to declare cross-scope work is through an explicit owner declaration. When a task touches non-dashboard files, the orchestrator requires this declaration to maintain auditable changes outside the dashboard/ subtree.

Why does my dashboard task require an explicit owner declaration?

An explicit owner declaration is required to ensure safe orchestration when tasks extend beyond the dashboard/ subtree. It enforces accountability and prevents unauthorized agents from modifying non-dashboard code.