Menu
Guide a consuming repository through `sc-lint-version` adoption using the authoritative consumer-integration workflow, existing CLI testability seams, existing simulators or transcripts, and only thin normalization hooks when unavoidable.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Orchestrate sc-lint sprint work where team-lead coordinates, clint is the sole developer, and quality-mgr enforces the QA gate.
Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.
Run the repo Rust TODO finder during sprint-end or integration review and turn every discovered TODO into a QA finding rather than deferred work.
Orchestrate pre-dispatch QA finding triage as team-lead. Launch one qa-triage agent per finding, collect phase-scoped Turtle records, aggregate by promoted branch, and only then dispatch branch-scoped fix assignments to clint.
Team-lead drives plan hardening after the current plan state already exists in repo docs.
Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, clint reviews, and integration branch strategy. This skill is for team-lead only, not for scrum-masters.
| name | sc-lint-version-adoption |
| version | 1.0.0 |
| description | Guide a consuming repository through `sc-lint-version` adoption using the authoritative consumer-integration workflow, existing CLI testability seams, existing simulators or transcripts, and only thin normalization hooks when unavoidable. |
Use this skill when a consuming repository is adopting the planned
sc-lint-version interface-checking line.
Always use:
docs/sc-lint/version-adoption.mdThat document is the authoritative adoption guide. Do not replace it with spread-out repo notes or ad hoc instructions.
This skill is narrowly scoped to sc-lint-version adoption only.
It covers:
It does not cover:
sc-lint feature planning[version.families.<family>].The consuming repo should provide:
[reporting.templates.<report_kind>]The consuming repo can run the planned interface-check flow and produce:
docs/sc-lint/version-adoption.mddocs/sc-lint/skill-authoring-constraints.mdMarketplace packaging for this adoption skill is deferred to C.5. This skill
document remains scoped to adoption workflow and does not own marketplace
publication shape.