util-ustagger

Tag untagged PRD.md sections with unique 9-character category-prefixed codes.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill util-ustagger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: util-ustagger
Source: https://github.com/rashidee/co2-skills/tree/main/skills/util-ustagger
Command: npx skills add https://github.com/rashidee/co2-skills --skill util-ustagger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tag untagged items in PRD.md files with unique 9-character IDs and validate no duplicates across User Stories, Non Functional Requirements, Constraints, References, and Test instructions.

Core Features & Use Cases

  • Automatically assign 9-character codes with category prefixes for top-level items in PRD.md.
  • Ensure no duplicate tags and maintain running numbers per category with a running interval of 3.
  • Supports tagging across User Stories, Non Functional Requirements, Constraints, References, and Tests; updates CHANGELOG.

Quick Start

Invoke the tool for an application and version, for example /util-ustagger hub_middleware v1.0.3, to tag top-level PRD items.

Frequently Asked Questions about util-ustagger

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

FAQPage Schema
How do I automatically tag PRD items with unique IDs to prevent duplicates?

To automatically tag PRD items, this tool assigns unique 9-character category-prefixed codes to top-level sections in PRD.md, validating no duplicates across User Stories, Non Functional Requirements, Constraints, References, and Tests.

What is the best way to ensure traceability across untagged Product Requirements Document sections?

Traceability across PRD sections is ensured by applying unique category-prefixed codes with a running number interval of 3 to top-level items, preserving existing tags and rejecting duplicates to maintain a clean numbering sequence.

How do I tag PRD requirements without overwriting existing tags or creating duplicate codes?

Tagging PRD requirements without overwriting existing tags works by scanning top-level items in PRD.md, preserving any existing codes, applying 9-character tags only to untagged items, and rejecting duplicate codes.

Does this PRD tagging tool update the CHANGELOG after assigning requirement tags?

Yes, PRD tagging updates the application's CHANGELOG accordingly after assigning unique 9-character codes to untagged top-level items across User Stories, Non Functional Requirements, Constraints, References, and Tests.

Can I use this for tagging Non Functional Requirements and Test instructions in a PRD.md file?

Yes, you can use this for tagging Non Functional Requirements and Test instructions alongside User Stories, Constraints, and References, applying category-prefixed 9-character codes to all top-level items in the PRD.md file.

What format do the unique requirement IDs take when tagging PRD sections?

Unique requirement IDs take the format of 9-character category-prefixed codes with a running number interval of 3, applied sequentially to top-level items within the PRD.md file to ensure traceability.