genichinandClaude Opus 4.8
2bb2db1a72
Add CLAUDE.md governance instructions, .claude command definitions, and .github skill/instruction set for the Agile iterative SDLC flow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
StagePilot Skills
Personal StagePilot skill pack for Hermes external skills.
This directory is configured as an external skill root and contains the reusable skills, shared conventions, and cross-skill metadata for the StagePilot SDLC workflow.
Purpose
StagePilot organizes work into a document-driven flow around:
- baseline bootstrap
- discovery
- requirements
- batch planning / design / implementation / verification
- release
- release feedback and next-discovery planning
These skills are intended to be reusable across repositories and machines, with versioned frontmatter so changes can be tracked over time.
Installation / usage on another machine
- Copy or clone this directory to the target machine.
- Point Hermes
config.yamlexternal skills setting at~/.stage-pilot/skills. - Reload skills:
/reload-skillsin-session, or- restart Hermes / start a new session.
Skill inventory
Stable core skills
bootstrap-baseline—1.0.1new-discovery—1.0.1draft-req—1.0.3
These are treated as the most reusable, foundational StagePilot workflow skills.
Near-stable skills
confirm-discovery—0.9.1confirm-req—0.9.1draft-batch—0.9.1
These are close to stable but may still get light structural refinement.
Maturing workflow skills
change-req—0.8.0confirm-batch-verification—0.8.0confirm-release—0.8.0draft-batch-design—0.8.0draft-batch-planning—0.8.0draft-batch-verification—0.8.0draft-release—0.8.1review-discovery—0.8.0suggest-batch-reqs—0.8.2
These are structured and usable now, but are expected to evolve as StagePilot usage expands.
Active evolution / orchestration skills
confirm-req-implemented—0.7.0run-batch-delivery—0.7.0run-batch-implementation—0.7.0run-sdlc—0.7.0
These involve orchestration or execution-heavy behavior and are expected to change more than drafting skills.
Early-support skills
capture-release-feedback—0.6.0suggest-next-discovery—0.6.0
These are useful but still relatively early in the overall workflow maturity.
Versioning policy
Semantic versioning is used loosely to describe workflow maturity:
0.6.x— useful early-support skill, likely to evolve significantly0.7.x— active execution/orchestration logic still evolving0.8.x— maturing drafting/decision workflow0.9.x— near-stable and expected to change lightly1.0.x— stable core skill suitable for broad reuse
Practical interpretation:
- patch bump (
x.y.Z) → wording fixes, metadata tweaks, examples, minor clarifications - minor bump (
x.Y.z) → meaningful behavior/structure expansion without redefining the role of the skill - major bump (
X.y.z) → significant workflow or contract change
Metadata conventions
Each StagePilot skill should include these frontmatter fields:
namedescriptionversionauthor: Justin Kolicense: privatemetadata.hermes.tagsmetadata.hermes.related_skills
Optional but commonly retained:
argument-hintuser-invocable
Recommended repository hygiene
If this directory is tracked in git, recommended companions are:
README.md— this fileCHANGELOG.md— top-level release notes for the skill pack- commits for every meaningful skill change
- optional tags when you want to snapshot a known-good pack revision
Last metadata normalization
- Date: 2026-05-22
- Author normalized to:
Justin Ko - Version fields reclassified by workflow maturity
- Cross-skill tags and related-skill metadata added to all StagePilot skills