Adaptive-dev-skill

Classify a new or materially changed software-development goal and submit its route decision to workflow-control-plane. Use at task intake when risk, strategy, SpecFlow/OpenSpec, context grounding, handoff, harness, or downstream skill selection must be decided; do not use for ordinary continuation when an active workflow manifest already selects the current stage skill. 当新开发目标进入、范围或风险实质变化、需要选择开发策略/Spec/上下文/交付流程时使用；已有 active workflow 的普通续作直接恢复当前 stage，不重复触发本 skill。

Coordinate role-based AI agents through agent rosters, work orders, context packets, artifact refs, and structured result contracts. Use when a software workflow needs multiple roles such as context researcher, spec writer, spec reviewer, technical designer, implementer, code reviewer, tester, verifier, or when the user wants an orchestrator to manage progress without manually copying context between sessions. 当需要多 Agent 协作、角色隔离、上下文投影、work order、artifact 驱动交接、进度监管或避免人工搬运上下文时使用。

Select and run changed-file-aware tests for software development loops, checkpoints, and completion gates. Use when a task should avoid repeatedly running the full unit suite, needs diff-based test impact selection, test cadence decisions, or must escalate from focused tests to broader verification. 当开发任务需要按 diff 跑增量测试、选择受影响单测、控制测试频率、避免每个 task 全量测试或判断何时升级为模块/全量验证时使用。

Owns workflow runtime state for adaptive AI coding tasks. Use when resolving route decisions, selecting versioned strategies, creating/updating workflow_manifest.json, validating artifact graphs, resuming interrupted workflows, applying specialist skill transition results, or enforcing strategy/stage/claim/state contracts. 当需要策略解析、workflow_manifest 单点写入、状态迁移、resume、artifact graph、stale 传播、claim ceiling 或工作流状态检查时使用。

Use when validating evidence manifests, deciding dev_done/integration_done/handoff_done claims, issuing verifier attestations, preventing completion overclaim, or requiring fresh consumer / real external verification. 当任务需要证据矩阵、交付验收、claim attestation、fresh consumer、real external、E2E/integration/system 证据或防止假完成时使用。

Initialize or repair a project AI coding harness: AGENTS.md, OpenSpec-first or Superpowers-fallback spec/design/plan routing, docs/evidence, Goal Loop Mode prompt, agent team roles, project-local skill, learning candidates, and delivery verification templates. Use when starting a new repo/product area, first MVP vertical slice, Large feature lacking current-truth docs, repeated user explanations, weak project agents, missing spec/technical-design/plan/evidence contracts, or when adaptive-dev-workflow routes to project harness initialization. 当需要项目初始化、目标模式、OpenSpec 优先或 Superpowers fallback 的 spec/technical design/plan/evidence、项目 agent 团队、项目 skill、AGENTS.md、交付验证或 Loop Engineering 基座时使用。

Use when a development task needs Analysis Pack, Context Manifest, context slicing, runtime audit, freshness checks, or sufficiency eval before implementation. 当任务需要深度阅读、上下文裁剪、Analysis Pack、Context Pack、allowed paths、freshness、runtime audit 或验证上下文是否足够时使用。

Use when repeated project knowledge, user corrections, quality dissatisfaction, SOP patterns, project skill updates, AGENTS.md updates, templates, or eval cases should be captured and promoted. 当需要沉淀项目经验、踩坑、用户反馈、项目 skill、AGENTS.md、模板、测试夹具或自动迭代 skill 时使用。

Use when raw intent must be turned into a reviewed spec before implementation, including OpenSpec adapter, pack-backed spec generation, lightweight spec generation, acceptance criteria, non-goals, and evidence plan. 当用户要求先写 spec、意图还没变成目标/边界/验收/测试，或 adaptive-dev-workflow 路由到 SpecFlow 时使用。

Bridge approved adaptive workflow artifacts into one exact native Superpowers skill without copying its methodology. Use only when workflow-control-plane lists a specific superpowers:* method for the active stage and its output must map back to that stage. 当 control plane 为当前阶段明确选择某个 Superpowers 原生 skill 时使用；不提供完整 Superpowers 工作流。

Use after an approved product spec and before implementation planning when a task needs none/embedded/standalone technical design, documentation topology, split design workspace, architecture boundaries, API/event/data/state contracts, security/migration/rollback/observability decisions, OpenSpec design.md reuse, design review, or design approval. 当 spec 已确认但还需要技术设计、文档分层、拆分 design workspace、架构边界、契约、状态/数据流、安全迁移回滚、可观测性、设计审查或 adaptive-dev-workflow 路由到 technical-design 时使用。