jared/cc-os

Watch

Fork 0

Add frontmatter registry doc + thin frontmatter CRUD skill #293

New issue

Closed

opened 2026-08-06 19:34:44 +00:00 by jared · 2 comments

jared commented

2026-08-06 19:34:44 +00:00

Owner

Context

From the 2026-08-06 file_locked grill session (follow-on to #292). cc-os has accumulated ad-hoc frontmatter metadata keys with no canonical registry: lint-style (os-sdlc), file_locked (#292 hook), hygiene: frozen (os-doc-hygiene), plus cc-architect's skill/agent frontmatter conventions. Decision: a canonical registry REFERENCE DOC plus ONE thin skill, not per-key skills.

Deliverable 1: registry doc

Co-located with the hook's owner: plugins/os-status/references/frontmatter-registry.md (or the 'os' successor plugin if the merge ticket has landed). Contents: every recognized metadata key, which file types it applies to (per-type attribute tables + global keys), exact format, and copy formulas (paste-ready examples). Documents at minimum: file_locked, lint-style, hygiene. cc-architect's references/conventions docs gain a cross-reference pointing here — cc-architect and other plugins defer to this registry when creating/editing markdown frontmatter, they do not duplicate it.

Deliverable 2: thin CRUD skill

One skill for all frontmatter CRUD; its body is mostly 'Read the registry, then apply it'. The skill DESCRIPTION must be written so plain phrases trigger it without the user remembering the word frontmatter — include triggers like 'lock this file', 'unlock this file', 'add/edit frontmatter', 'set lint-style'. The user should never need to memorize the skill name; the description does the remembering.

Constraints

NO dependency from the #292 hook to this skill or vice versa — the hook is a standalone script; deleting either leaves the other fully functional. They share only the file-format convention documented in the registry.
Skill name/namespace is PENDING the os-merge ticket's naming ADR (noun-first, e.g. /os:frontmatter or /os:frontmatter-edit). Do not name it under the old verb-first convention.
Execution order: implement AFTER #292 (hook) and AFTER the os-merge ticket (naming ADR + final plugin home), i.e. third of the three.
Keep the skill thin: no logic that belongs in the registry doc; adding two frontmatter lines is an edit any model does from the registry schema.

## Context From the 2026-08-06 file_locked grill session (follow-on to #292). cc-os has accumulated ad-hoc frontmatter metadata keys with no canonical registry: lint-style (os-sdlc), file_locked (#292 hook), hygiene: frozen (os-doc-hygiene), plus cc-architect's skill/agent frontmatter conventions. Decision: a canonical registry REFERENCE DOC plus ONE thin skill, not per-key skills. ## Deliverable 1: registry doc Co-located with the hook's owner: plugins/os-status/references/frontmatter-registry.md (or the 'os' successor plugin if the merge ticket has landed). Contents: every recognized metadata key, which file types it applies to (per-type attribute tables + global keys), exact format, and copy formulas (paste-ready examples). Documents at minimum: file_locked, lint-style, hygiene. cc-architect's references/conventions docs gain a cross-reference pointing here — cc-architect and other plugins defer to this registry when creating/editing markdown frontmatter, they do not duplicate it. ## Deliverable 2: thin CRUD skill One skill for all frontmatter CRUD; its body is mostly 'Read the registry, then apply it'. The skill DESCRIPTION must be written so plain phrases trigger it without the user remembering the word frontmatter — include triggers like 'lock this file', 'unlock this file', 'add/edit frontmatter', 'set lint-style'. The user should never need to memorize the skill name; the description does the remembering. ## Constraints - NO dependency from the #292 hook to this skill or vice versa — the hook is a standalone script; deleting either leaves the other fully functional. They share only the file-format convention documented in the registry. - Skill name/namespace is PENDING the os-merge ticket's naming ADR (noun-first, e.g. /os:frontmatter or /os:frontmatter-edit). Do not name it under the old verb-first convention. - Execution order: implement AFTER #292 (hook) and AFTER the os-merge ticket (naming ADR + final plugin home), i.e. third of the three. - Keep the skill thin: no logic that belongs in the registry doc; adding two frontmatter lines is an edit any model does from the registry schema.

jared added the

ready-for-agent

labels

2026-08-06 19:34:44 +00:00

jared referenced this issue

2026-08-06 19:47:17 +00:00

Add file_locked frontmatter guard hook for hand-tuned files #292

jared commented

2026-08-06 20:26:14 +00:00

Author

Owner

Work started on main: adding plugins/os/references/frontmatter-registry.md + /os:frontmatter skill per ticket spec.

jared commented

2026-08-06 20:29:41 +00:00

Author

Owner

Resolution

Done: Registry doc plugins/os/references/frontmatter-registry.md (file_locked, hygiene, lint-style) + thin /os:frontmatter-edit skill; cc-architect layout docs cross-reference the registry.

Evidence: Commit cd5e4f3 on main; both os test suites green; every registry claim verified against its reader (pre_tool_use.py, scanner.py _is_frozen, config.rb metadata_value).

Follow-ups: Symmetric registry cross-refs from os-doc-hygiene/os-aidd-lint docs considered and dropped — ticket scoped cross-refs to cc-architect only.

## Resolution **Done:** Registry doc plugins/os/references/frontmatter-registry.md (file_locked, hygiene, lint-style) + thin /os:frontmatter-edit skill; cc-architect layout docs cross-reference the registry. **Evidence:** Commit cd5e4f3 on main; both os test suites green; every registry claim verified against its reader (pre_tool_use.py, scanner.py _is_frozen, config.rb metadata_value). **Follow-ups:** Symmetric registry cross-refs from os-doc-hygiene/os-aidd-lint docs considered and dropped — ticket scoped cross-refs to cc-architect only.

jared closed this issue

2026-08-06 20:29:41 +00:00

jared referenced this issue from a commit

2026-08-07 10:59:06 +00:00

os: frontmatter registry reference doc + /os:frontmatter-edit thin CRUD skill (#293)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

jared/cc-os#293

No description provided.

Rows
Columns