devtool-workflow · GeorgeQLe - Agent Skill

01 前言 Front Matter

name: devtool-workflow
type: planning
version: v0.3
invocation: orchestrator
description: Use only for developer-facing tools, libraries, SDKs, CLIs, APIs, and infrastructure products
visual_tier: visual
context_intake: artifact_only
required_conventions: [ "alignment-page" ]

02 资源文件 13

参考文档architecture-decision-template.md337 B
其他customize.toml1.6 KB
资产文件data/domain-complexity.csv2.1 KB
资产文件data/project-types.csv758 B
参考文档steps/step-01-init.md6.4 KB
参考文档steps/step-01b-continue.md6.1 KB
参考文档steps/step-02-context.md8.4 KB
参考文档steps/step-03-starter.md11.7 KB
参考文档steps/step-04-decisions.md10.0 KB
参考文档steps/step-05-patterns.md10.7 KB
参考文档steps/step-06-structure.md10.9 KB
参考文档steps/step-07-validation.md11.4 KB
参考文档steps/step-08-complete.md3.3 KB

03 SKILL.md 正文

Devtool Workflow

Invoke as $devtool-workflow.

Use this skill when the project is primarily developer-facing.

Process

Read .agents/project.json and confirm project_type is devtool.
If the devtool pack is not enabled, install it with scripts/pack.sh install devtool from this source checkout, or npx skillpacks install devtool from the project shell when using the published package.
Route research through developer workflow, integration, DX, adoption, positioning, monetization, and docs checks.

Output

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> using the ## Next-Skill Routing rules below.

Alignment Page

Follow the shared alignment-page convention via the packaged convention resolver; output path is alignment/devtool-workflow-{topic}.html. By default, report results inline and write only this skill's normal durable artifacts; create an alignment page only when explicitly requested or when a concrete clarification/review need cannot be handled cleanly inline.