Devtool Workflow
Invoke as $devtool-workflow.
Use this skill when the project is primarily developer-facing.
Scope-First Router Workflow
This skill is the devtool AFPS scope/router orchestrator. It does not perform downstream research itself and it does not route to downstream devtool skills until the user has approved the route and scope through compiled YAML.
- Stage 0 - Interrogation. Build the stage-zero HTML interrogation page for devtool identity, target developer audience, buyer/champion/operator distinctions, available evidence, maturity, constraints, non-goals, and desired AFPS route. Loop until the confidence gate passes and consume the compiled interrogation YAML before building the route/scope alignment page.
- Stage 1 - Route and scope approval. Inspect only enough repository and user-provided context to classify the project as developer-facing, identify missing devtool artifacts, propose the first concrete next skill, and name the evidence or decision that makes it first. Build
alignment/devtool-workflow-{topic}.html as a review page with the proposed route, scope, assumptions/confidence, missing artifact matrix, candidate next skills, and approval gates. Stop for final compiled YAML approval. Do not include Recommended next skill, Recommended next command, or downstream routing language before approval YAML is consumed.
- Stage 2 - Confirmed routing. Only after approved compiled YAML with no unresolved
needs-clarification, unresolved down feedback, or other unresolved negative feedback, apply approved edits, convert the alignment page to confirmed with the approval record preserved, and emit exactly one next devtool command using the approved route. If the route is still ambiguous after feedback, keep the page in review and ask for the missing decision instead of guessing.
Default sequence when no more specific approved route overrides it: $devtool-user-map, $devtool-integration-map, $devtool-dx-journey, $devtool-adoption, $devtool-positioning, $devtool-monetization, $devtool-docs-audit.
Output
After final compiled YAML approval is consumed and the alignment page is converted to confirmed, recommend the next single devtool-pack skill to run and explain the missing artifact or decision that makes it next. In the final response, include Recommended next skill: <command> only after that approval. Before approval, the next action is review of the HTML alignment page.
Alignment Page
Follow the shared alignment-page convention via the packaged convention resolver; output path is alignment/devtool-workflow-{topic}.html.
Interrogation Page
Follow the shared interrogation-page convention via the packaged convention resolver; output path is interrogation/devtool-workflow-r{N}-{branch}.html. Before producing research, run the stage-zero interrogation loop, starting with the assumptions manifest as round 1, and loop until the confidence gate passes. This skill cannot advance to stage one until the confidence gate passes with at least one completed interrogation round and every interview area covered or waived. Each round page must contain at least one genuinely open input (data-open-input).
Default Shipping Contract
Follow the shared shipping contract convention in CLAUDE.md.
1---2name: devtool-workflow3description: Use only for developer-facing tools, libraries, SDKs, CLIs, APIs, and infrastructure products4---56# Devtool Workflow78Invoke as `$devtool-workflow`.910Use this skill when the project is primarily developer-facing.1112## Scope-First Router Workflow1314This skill is the devtool AFPS scope/router orchestrator. It does not perform downstream research itself and it does not route to downstream devtool skills until the user has approved the route and scope through compiled YAML.15160. **Stage 0 - Interrogation.** Build the stage-zero HTML interrogation page for devtool identity, target developer audience, buyer/champion/operator distinctions, available evidence, maturity, constraints, non-goals, and desired AFPS route. Loop until the confidence gate passes and consume the compiled interrogation YAML before building the route/scope alignment page.171. **Stage 1 - Route and scope approval.** Inspect only enough repository and user-provided context to classify the project as developer-facing, identify missing devtool artifacts, propose the first concrete next skill, and name the evidence or decision that makes it first. Build `alignment/devtool-workflow-{topic}.html` as a `review` page with the proposed route, scope, assumptions/confidence, missing artifact matrix, candidate next skills, and approval gates. Stop for final compiled YAML approval. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language before approval YAML is consumed.182. **Stage 2 - Confirmed routing.** Only after approved compiled YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, apply approved edits, convert the alignment page to `confirmed` with the approval record preserved, and emit exactly one next devtool command using the approved route. If the route is still ambiguous after feedback, keep the page in `review` and ask for the missing decision instead of guessing.1920Default sequence when no more specific approved route overrides it: `$devtool-user-map`, `$devtool-integration-map`, `$devtool-dx-journey`, `$devtool-adoption`, `$devtool-positioning`, `$devtool-monetization`, `$devtool-docs-audit`.2122## Output2324After final compiled YAML approval is consumed and the alignment page is converted to `confirmed`, recommend the next single devtool-pack skill to run and explain the missing artifact or decision that makes it next. In the final response, include `Recommended next skill: <command>` only after that approval. Before approval, the next action is review of the HTML alignment page.2526## Alignment Page2728Follow the shared alignment-page convention via the packaged convention resolver; output path is `alignment/devtool-workflow-{topic}.html`.2930## Interrogation Page3132Follow the shared interrogation-page convention via the packaged convention resolver; output path is `interrogation/devtool-workflow-r{N}-{branch}.html`. Before producing research, run the stage-zero interrogation loop, starting with the assumptions manifest as round 1, and loop until the confidence gate passes. This skill **cannot advance to stage one until** the confidence gate passes with at least one completed interrogation round and every interview area covered or waived. Each round page must contain at least one genuinely open input (`data-open-input`).3334## Default Shipping Contract3536Follow the shared shipping contract convention in CLAUDE.md.
GeorgeQLe