By task¶
Task-oriented landing page: groups skills and agents by user intent rather than by delivery-lifecycle phase. Hand-curated; rubrics grow as more artifacts expose use_when metadata.
Note: Only the pilot-migrated artifacts currently appear here. For anything not yet listed, browse the phase-grouped Skills and Agents indexes, or the Tag index for thematic browsing.
Open or land a pull request¶
- Open a draft PR on the current feature branch →
pull-request-create. Verifies the branch is in sync withdevelop, composes a Conventional-Commits title and the five-section body, autolinks any touched specs, then runsgh pr create. - Land an already-open draft PR on
develop→pull-request-merge. Delegates pre-merge review, derives labels from the commit type and touched paths, flips draft → ready, appliesautomerge, and verifies the squash-merge commit landed.
Author or audit a specification¶
- Write, translate, or refresh a spec under
spec/→spec. Keeps every configured language tree in sync with the canonical source, regenerates the spec index, and de-duplicates against existing coverage. - Audit a spec before downstream implementation →
spec-readiness-reviewer. Read-only audit for contradictions, audience fit, requirement-to-AC coverage, and ghost references to non-existent specs. Severity-sorted report; never edits.
Author a Claude Code skill¶
- Scaffold or revise a
nolte-sharedskill folder →skill-management. Writes theSKILL.mdtemplate with valid frontmatter, then chains toclaude-plugin-developerfor the spec-conformant body draft.
Pick a skill vs. an agent¶
When the task could plausibly live in either form, read the skill-vs-agent spec first—it captures the decision dimensions (orchestration vs. specialisation, context-window pressure, parallelism, interactivity) that drive the choice.