Manage user stories as structured JSON with role-based access control.
npx skills add https://github.com/VitorAndTxr/omni-sw --skill backlog-vitorandtxr
Please help me install this Agent Skill. Skill: backlog Source: https://github.com/VitorAndTxr/omni-sw/tree/main/skills/backlog Command: npx skills add https://github.com/VitorAndTxr/omni-sw --skill backlog-vitorandtxr
Backlog management system — Manages user stories as structured JSON with role-based access control, replacing markdown-based BACKLOG.md. Provides CRUD operations for user stories, status tracking, acceptance criteria, dependency maps, and auto-generated markdown summaries. Enforces agency permissions: only po/pm create stories, only po/pm/tl edit descriptions, all agents can change status. Supports migration from legacy markdown BACKLOG.md via review teams. Use when: (1) any agent needs to create, (2) agent mentions backlog, user story, US-, acceptance criteria, story status, (3) po/pm is producing backlog in Plan phase, (4) any agent needs to query stories by status/feature/priority, (5) generating BACKLOG.md summary from JSON data, (6) migrating an old docs/BACKLOG.md to the new JSON format.
Create your backlog using backlog.json and start mutating stories with backlog_manager.py.
High-intent search queries and answers about installing and using this skill.
You can migrate legacy markdown BACKLOG.md to structured JSON using the system's built-in migration path via review teams. This converts flat markdown into structured JSON user stories with status tracking and dependencies.
Backlog user story permissions enforce that only po/pm roles create stories, po/pm/tl edit descriptions, and all agents update status. This role-based access control maintains structured backlog integrity.
Yes, the system auto-generates a markdown BACKLOG.md summary from the JSON-backed user stories. It uses backlog.json as the source of truth and renders a readable markdown view of the structured data.
The backlog system supports dependency tracking and status transitions for agile user stories. It provides full CRUD operations across planning, implementation, and testing phases, mapping dependencies and tracking statuses within the JSON schema.
Using JSON instead of markdown for agile user stories enables structured data schemas, dependency maps, and role-based permissions. This replaces flat markdown files with a queryable source of truth for status tracking and audits.
panayiotismInitialize, upgrade, or migrate the claude-harness plugin in a project.
slabgorbGenerates epic and story context documents from sprint data with YAML frontmatter.
MarkusonParse epic and story markdown to generate sprint-status.yaml tracking files.
doolinCreate Markdown project management templates under a .development directory.
