What problem does it solve?
Teams running multiple planning agents (RAI, Security, SSSC, Accessibility, Privacy) need consistent work-item formats when handing off backlog items to Azure DevOps or GitHub, but each planner previously restated the same template skeletons, sanitization rules, and ID conventions.
Core Features & Use Cases
- Dual-format templates: Provides HTML skeletons for ADO work items and YAML-plus-markdown skeletons for GitHub issues, with per-planner field blocks.
- Content sanitization protocol: Applies five rules to strip internal paths, state JSON, and tracking references before work items reach external systems.
- Autonomy-tier vocabulary: Defines the canonical manual/supervised/autonomous tiers and maps divergent per-planner vocabularies for cross-planner reporting.
- Use Case: A security planner finishes a threat-modeling phase and emits sanitized GitHub issues using the shared template, disclaimer block, and
WI-SEC- ID convention without duplicating format logic.
Quick Start
Ask the planner to generate the backlog handoff work items for ADO or GitHub using the shared backlog templates.