| name | agentic-coding-inventory |
| description | Classify Builder workspace inventory documents, supporting sources, and UNKNOWN repair outcomes without upgrading ordinary Markdown into formal assets. |
Agentic Coding Inventory
Use this skill when a Builder workspace request mentions inventory, reference
documents, supporting-source selection, classification drift, imported docs,
seed docs, stale inventory, or UNKNOWN repair.
Required Context
docs/solutions/l1/roadmap/builder-workspace-baseline-rules.md
skills/agentic-coding-inventory/rules/inventory-classification.md
skills/agentic-coding-inventory/rules/supporting-source.md
skills/agentic-coding-inventory/rules/unknown-repair.md
skills/agentic-coding-inventory/templates/inventory.yaml
Workflow
- Run
agentic-spec inventory scan --workspace <path> when the inventory is
missing or stale.
- Use the classification rules to decide whether non-formal Markdown is
reference, supporting-source, ignored, or needs-review.
- Run
agentic-spec inventory repair --workspace <path> when diagnostics show
fallback UNKNOWN assets.
- Explain UNKNOWN repair results to the user and keep repaired documents out of
the formal Builder Assets list unless a later derivation upgrades them.
- Run
agentic-spec doctor --workspace <path> before reporting readiness.
Guardrails
Inventory scan and repair must not modify Markdown body text or reference
frontmatter.
Reference frontmatter may be written only during phase derivation or
normalization, not during inventory refresh.
Do not generate roadmap phase splits, formal L1/L2/L3 assets, or prototype
assets from this skill.