register

Automated brief creation parses arguments, selects templates, computes sequential IDs, and writes populated markdown files to the project briefs folder. This eliminates manual tracking and ensures consistent metadata for bugs, features, migrations, and technical debt.

Tracking technical debt and migrations is best handled by mapping brief types to standard prefixes like TD and MG, then generating sequential markdown files from predefined templates. This approach maintains consistent metadata and provides a clear starting point for development work.

An igris_brain MCP connection is not required to register briefs. The skill calls the igris_brief_sync MCP when available but fails silently if the brain is unreachable, allowing local brief generation and blocker tracking to proceed normally without external dependencies.

Yes, you can automatically add P0 and P1 blockers to session/BLOCKERS.md during brief creation. When registering a brief with high priority items, the skill optionally appends these blockers to the session file to surface immediate impediments alongside the generated markdown brief.

Sequential ID assignment works by scanning the ai/briefs/ directory to find the next available numeric ID for the selected prefix. It combines this ID with the prefix and a slugged title to create a unique filename for each new bug, feature, migration, or technical debt entry.

If a specific template is missing, the brief generation falls back to a default template to populate standard fields like Status, Priority, Created date, and Title. This ensures brief creation can proceed even without a customized template for every prefix.