skills.rest
FernanSuoza
FernanSuozaCOMMUNITY
Explore all skills by this author →
GitHub

gov-id-registry

Reserve and validate governed artifact identifiers using id_rules.yaml and id-counters.json.

Updated Mar 22, 2026
Search Tags:#validation#traceability#id-registry#artifact-ids#identifier-generation#registry-counters
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill gov-id-registry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gov-id-registry
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/gov-id-registry
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill gov-id-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve?

Centralizes and enforces consistent reservation, validation, and documentation of project artifact identifiers to prevent collisions, ghost IDs, and format drift across a delivery workspace.

Core Features & Use Cases

  • Deterministic ID reservation for prefixes such as REQ, US, HUS, BUG, ADR using a shared counter file so IDs remain sequential and auditable.
  • Format validation and listing of supported prefixes and inline-marker semantics to enforce width, separator, and artifact vs inline-marker rules.
  • Registry updates that persist counter state in execution-plan/registry/id-counters.json and rely on id_rules.yaml for prefix metadata.

Quick Start

Run the generate_ids.py script in this skill with the desired prefix and optional count to reserve new IDs or use --validate to check an existing ID.

Frequently Asked Questions about gov-id-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reserve sequential artifact identifiers for requirements and bugs?▼

To validate an existing artifact ID, run generate_ids.py with the --validate flag. It checks the provided ID against prefix metadata in id_rules.yaml, verifying zero-padded numeric width, separator conventions, and artifact versus inline-marker rules to prevent format drift.

What is the best way to prevent ID collisions and ghost IDs in a delivery workspace?▼

You need pyyaml installed to parse prefix metadata from id_rules.yaml. Your environment must also support writing to execution-plan/registry/id-counters.json to persist deterministic counter updates for artifact and inline-marker ID generation.

When do I need governed artifact identifiers with inline markers?▼

You need governed artifact identifiers with inline markers when executing delivery and backlog workflows that require canonical IDs. This applies to tracking requirements, user stories, bugs, ADRs, and inline markers across the execution-plan registry to enforce width and separator conventions.

Does this ID registry tool support custom prefix rules for artifact validation?▼

Yes, the ID registry supports custom prefix rules for artifact validation. Prefix metadata is defined in id_rules.yaml, allowing you to configure and enforce specific prefix rules, zero-padded numeric widths, and separator conventions for your governed artifact identifiers.

Related Skills

Explore More Product & Management Skills→
yesplease-studioyesplease-studio
2

prd-loop

Externalizes orchestration cycle state into LOOP-STATE.md and updates batch pointers, debt counters, fan-out registry, decisions, signatures, and summaries.

Official
Advanced
bbolek-apbbolek-ap

create-work-breakdown

Generate and extend backlog files under .project/backlog/ using canonical WBS templates.

Community
Advanced
Covcloud-LLCCovcloud-LLC

pjm

Coordinate multi-session AI development workflows across git repositories.

Official
Advanced
carrot-foundationcarrot-foundation
1

rule-schema-versioning

Enforce centralized JSON Schema $id versioning across builds and runtime.

Official
Advanced