governance-kit-skill-authoring
Use when creating, renaming, reviewing, or updating repo-local skills for Agentic Doc Governance Kit, including skill frontmatter, required sections, registry updates, generated footprint entries, README project shape, changelog notes, and skills integrity checks. Use this whenever the user asks to turn a workflow into a skill or add a skill to this kit.
- License 许可
- MIT
- 最近更新
- 2026-07-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- governance-kit-skill-authoring
- description
- Use when creating, renaming, reviewing, or updating repo-local skills for Agentic Doc Governance Kit, including skill frontmatter, required sections, registry updates, generated footprint entries, README project shape, changelog notes, and skills integrity checks. Use this whenever the user asks to turn a workflow into a skill or add a skill to this kit.
03 SKILL.md 正文
Governance Kit Skill Authoring
Use this skill to add or update kit-provided repo-local skills in a way that will survive initialization, packaging, and integrity checks.
Scope
- Create or update the correct skill root:
.codex/skills/<skill-name>/SKILL.mdfor kit-maintenance skills, ortemplates/.codex/skills/<skill-name>/SKILL.mdfor skills installed into target repos - Write triggering frontmatter descriptions
- Keep skill instructions operational and concise
- Update
templates/.codex/skills/README.md - Update
.agentic-doc-governance.jsongenerated required paths - Update README project shape when generated skills are listed there
- Update changelog when the skill is user-visible
- Run skills and generated-footprint checks
This skill handles skills shipped by this kit. It does not install personal user skills outside the repo.
Default workflow
- Choose a narrow skill name with lowercase kebab-case.
- Write frontmatter:
name: exact directory namedescription: include both what it does and when to use it
- Keep the skill body focused on repeatable agent behavior, not long background explanation.
- Include the standard headings required by this repo's skills checker:
## Scope## Default workflow## Output format
- Prefer command examples that work in both local-checkout and package-installed contexts when the skill will run outside this repo.
- Add the skill to the matching registry:
.codex/skills/README.mdfor kit-maintenance skills, ortemplates/.codex/skills/README.mdfor shipped target-repo skills. - Add the
SKILL.mdpath to.agentic-doc-governance.jsonundergenerated.requiredPaths. - If the skill is installed into target repos and README shows the generated project tree, add the skill to that tree.
- Add a changelog entry if the skill changes shipped behavior or user-visible templates.
- Run:
node scripts/skills-integrity-check.mjs
node scripts/docs-integrity-check.mjs --check-generated
npm test
- Review the diff for unintended file churn.
Output format
Report:
- skill name and path
- trigger intent
- files updated
- generated-footprint and registry status
- verification commands and results
- any follow-up test cases or known limitations
04 同仓库更多 Skills
implementation-surface
Use when implementing or reviewing project-specific application code after feature lifecycle handoff.
governance-kit-operator
Use when installing, refreshing, or operating Agentic Doc Governance Kit in a target repo, including init dry-runs, generated governance files, feature lifecycle CLI usage, checks, and final user reports. Use this whenever the user asks an AI agent to set up this kit, apply it to another project, initialize governance docs, create governed feature work, or explain the operational workflow.
feature-readiness
Use when deciding whether a planned feature can move into implementation, including blocker analysis and artifact decisions.
feature-lifecycle
Use when adding, planning, updating, verifying, closing out, archiving, or relocating a project feature under the repo's documentation governance model.
feature-lifecycle
Example lifecycle skill.
governance-kit-target-smoke
Use when validating that Agentic Doc Governance Kit initializes correctly into a target repository, including init dry-runs, generated file presence, installed skills, docs checks, skills checks, and optional feature lifecycle CLI smoke tests. Use this whenever the user asks to test install output, verify init behavior, or confirm generated templates work in a target repo.