prd-slice
PRD Slice
Break a PRD into independently-deliverable vertical slices (tracer bullets) and push them to the right tracker.
Tracker reference files — use the dedicated skill when available; fall back to the reference file only when it isn't:
| Tracker | Preferred source | Fallback (skill absent) |
|---|---|---|
| Azure DevOps | azure-devops-cli skill (if loaded) |
references/azure-devops.md |
| GitHub Issues | gh-cli skill (if loaded) |
references/github.md |
| Jira | — | references/jira.md |
The dedicated skills (gh-cli, azure-devops-cli) carry richer, up-to-date platform context. When one is present in your available_skills, use it and skip the reference file — loading both is redundant and wastes context.
Scope
In scope: reading a PRD from a tracker, proposing and refining vertical slices with the user, creating work items in dependency order.
More from yldgio/vibe-grimoire
pre-mortem
>-
13create-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
11setup-repo
>-
11plan-from-prd
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
11tdd
>-
9adr
Create an Architectural Decision Record (ADR) to formally document a significant technical or architectural choice. Use whenever a user says "write an ADR", "document this decision", "record why we chose X", "capture this architecture choice", "explain why we went with Y", "document the trade-offs", "write up this tech decision", or makes any significant architectural choice that future teammates will need to understand. Also use proactively when you observe a meaningful decision being made during a session — even if the user hasn't explicitly asked for an ADR. ADRs prevent teams from re-debating settled choices and preserve context that would otherwise become tribal knowledge lost to future maintainers.
7