harness-bootstrap

Route ambiguous harness tasks to specialized workflows via path-based classification.

18|Updated Feb 14, 2020
One-click install
npx skills add https://github.com/subroh0508/colormaster --skill harness-bootstrap-subroh0508
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-bootstrap
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/archived/harness-bootstrap
Command: npx skills add https://github.com/subroh0508/colormaster --skill harness-bootstrap-subroh0508

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This archived Skill shows how ambiguous harness requests were routed to the correct Phase A workflow, so early bootstrap work could be classified instead of handled manually or inconsistently.

Core Features & Use Cases

  • Path-based task classification: Distinguishes ADR drafting, rules updates, docs expansion, Skill implementation, lint setup, module removal, and retro aggregation by the requested path.
  • Workflow delegation: Directs each task type to the appropriate specialized skill or rule set once those capabilities exist.
  • Historical reference: Preserves the original bootstrap and retro handling logic for understanding how harness operations were structured during Phase A.

Quick Start

Use this archived skill as a reference to identify the correct specialized workflow for a harness request and do not invoke it for new work.

Frequently Asked Questions about harness-bootstrap

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

FAQPage Schema
How do I classify ambiguous harness tasks for workflow routing?

Ambiguous harness tasks are classified by path-based routing to distinguish ADR drafting, lint setup, module removal, and retro aggregation workflows. Once identified, the task is directed to the appropriate specialized skill or rule set instead of being executed directly.

What is path-based task classification for bootstrap workflows?

Path-based task classification is a routing mechanism that identifies requested paths to distinguish bootstrap operations like documentation expansion, rules updates, and Skill creation. It delegates each identified task type to the appropriate specialized workflow.

When do I need dry-run decision guidance for harness operations?

Dry-run decision guidance is needed when routing ambiguous harness tasks to ensure safe delegation to specialized skills. It provides evaluation logic to determine whether a bootstrap operation should execute or simulate.

Does harness-bootstrap handle ADR drafting and retro aggregation directly?

Harness-bootstrap does not handle ADR drafting or retro aggregation directly. It routes these classified bootstrap tasks to specialized skills and rule sets for execution once the appropriate capabilities are identified.

Can I use harness-bootstrap for new module removal and lint setup tasks?

Harness-bootstrap is an archived reference for Phase A bootstrap scenarios and should not be invoked for new module removal or lint setup work. It preserves historical routing logic to identify the correct specialized workflow for these tasks.

Why does my harness workflow classification route to the wrong specialized skill?

Harness workflow classification relies on path-based task classification to route correctly. If the requested path is ambiguous, the routing logic may fail to distinguish between ADR drafting, rules updates, and Skill creation workflows.