full-fixture
Full positive fixture — every reserved frontmatter field used at least once.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- full-fixture
- calls
- [ "sub/SKILL.md" ]
- scope
- global
- inputs
- [ "input one", "input two" ]
- parent
- full-fixture
- outputs
- [ "output one" ]
- excludes
- [ "mutually-exclusive-skill" ]
- requires
- [ "prereq one" ]
- triggers
- [ "fixture", "full" ]
- runs_after
- [ "other-skill" ]
- visibility
- public
- description
- Full positive fixture — every reserved frontmatter field used at least once.
- runs_before
- [ "later-skill" ]
- kata_surface
- embedded
- calls_dynamic
- [ { "source": "issue.tier3_skills", "constraint": "skills under eng/" } ]
- artifact_class
- skill
- governing_question
- How do we prove the schema accepts every reserved field together?
02 资源文件 2
03 SKILL.md 正文
Full fixture
Used by scripts/ci/validate-skill-frontmatter.sh --self-test (#301 AC8) to
prove the schema accepts every reserved field, an unknown package-local
key (parent:), and a calls target whose existence is checked relative
to the package skill root.
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.
receipt-stream
Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd/iterations/INDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.
mid-flight
Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin/main while α/β polling sessions are in-flight.