agentsclimarketplace
Sign in

Subagent driven change

Skill jsuvic/agent-profile/fixtures/subagent-driven-development/expected/.agents/skills/subagent-driven-change

Use when a scoped implementation can be delegated to an implementation subagent and then independently reviewed for spec compliance before code quality.From its SKILL.md

Install
npx -y skills add jsuvic/agent-profile --skill subagent-driven-change

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 498 tokens by cl100k_base, as published. Nobody here has run it

<!-- Generated by Agent Profile Compiler. Do not edit by hand. -->

Subagent-Driven Change

Preconditions

Use this workflow only when the task has a clear spec, acceptance criteria, and file ownership. Keep tightly coupled or architectural decisions in the parent session unless the user explicitly asks for delegation.

Required subagents: implementer, spec-reviewer, and code-quality-reviewer.

Fresh Context

Each subagent prompt must include the full task text, relevant spec excerpts, non-goals, acceptance criteria, file ownership, constraints, expected tests, and any command limits. Do not rely on hidden chat history or a previous subagent's memory.

Flow

  1. Dispatch implementer with one bounded task and the complete context it needs.
  2. If implementer returns BLOCKED or NEEDS_CONTEXT, resolve that before continuing.
  3. If implementer returns DONE_WITH_CONCERNS, read the concerns before review and decide whether to fix, narrow scope, or continue.
  4. Dispatch spec-reviewer with the original task, relevant spec excerpts, changed files, and implementer report.
  5. Fix or escalate every spec-review issue before requesting code-quality review.
  6. Dispatch code-quality-reviewer only after spec review reports compliance.
  7. Fix Critical and Important code-quality issues before handoff, or document why a finding is intentionally deferred.
  8. Run the relevant tests, golden tests, and doctor/check commands required by the spec before final response.

Status Values

Implementation worker status values: DONE, DONE_WITH_CONCERNS, BLOCKED, NEEDS_CONTEXT.

Spec reviewer status values: COMPLIANT, ISSUES_FOUND, NEEDS_CONTEXT.

Code-quality reviewer status values: ACCEPTABLE, ISSUES_FOUND, NEEDS_CONTEXT.

Safety

  • Do not ask subagents to commit, push, create branches, install dependencies, read secrets, contact production systems, or upload source unless the user explicitly requested that action.
  • Do not accept an implementation report without reading reviewer findings.
  • Do not run code-quality review before spec-compliance review passes.
  • Keep generated files deterministic and lockfile-tracked.

Output

Final handoff must list what changed, tests run, contract impact, security impact, remaining risks or TODOs, and whether the spec acceptance criteria are fully met.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.