DATA-AI-XYZ
Official@DATA-AI-XYZ
DATA-AI-XYZ publishes the Tandem PM Operating Kit: 32 Claude Code skills governing the full product lifecycle from OKRs and PRDs through epics, stories, testplans, and phase retrospectives.
Agent Skills by DATA-AI-XYZ
Showing 32 vetted skills indexed across 1 GitHub repositories.
session-start
Loads active project context from markdown artefacts to orient a new Claude Code session.
install
Installs the Tandem PM kit by materializing folder trees, seed files, scripts, and dashboard.
execute-batch
Executes a batch of stories from an implementation strategy with atomic per-story finalisation and failure recovery.
core
Enforces project-management conventions for markdown artefacts, status gates, and lifecycle commands.
execution-strategist
Groups an epic's stories into phased execution chats and autopilot runs as a markdown report and JSON sidecar.
update
Refresh kit-owned templates, standards, and tooling in an installed Tandem project without touching user artefacts.
mode
Sets and enforces a project-global conversation mode across joined chat sessions.
draft-epic
Drafts an Epic markdown file from an OKR key result or PRD section with mandatory strategic linkage.
plan-drift
Traces requirements to stories bidirectionally and reports coverage gaps and drift.
path-scope-example
Demonstrates paths-scoped skill loading and provides an ADR-authoring checklist for decision records.
triage-backlog
Verifies backlog items against the current codebase and rules each keep, delivered, duplicate, or retired.
reflect
Generates end-of-session reflection proposals for updating CLAUDE.md, SOP.md, and PROJECT-CONTEXT.md files.
document
Generates five markdown documentation files from project context, epics, stories, and ADRs.
execute-story
Implements a Ready story's acceptance criteria while filing ADRs and BUGs during execution.
split-into-features
Decomposes an approved Epic into numbered Feature markdown files with acceptance criteria.
weekly-monitor
Generates weekly project monitor updates with delta metrics, stall flags, and dashboard regeneration.
split-into-stories
Decompose a Feature into Stories with paired Testplans in one response.
start-phase
Opens a project phase by gating entry conditions and cutting a phase branch off main.
write-outcomes
Generates one plain-English founder-outcome line from an artefact's technical content.
draft-okrs
Draft quarterly OKR markdown files from a North Star strategy document.
refine-backlog
Gate backlog items and stories through a Definition of Ready checklist before promotion.
critique
Reviews planning artefacts against per-type quality checks and reports severity-ranked findings.
draft-prd
Drafts a Product Requirements Document from strategy sources into a structured markdown file.
execute-batch-parallel
Executes independent stories concurrently via scoped sub-agents with single-writer board reconciliation.
Frequently Asked Questions About DATA-AI-XYZ
FAQPage SchemaWhat tasks can I accomplish with DATA-AI-XYZ's Tandem PM kit?▼
You can draft OKRs and PRDs, decompose epics into features and story-testplan pairs, refine backlog items through Definition of Ready, execute stories and testplans with automatic bug filing, run weekly monitors and monthly retros, and drive entire phases unattended via the autopilot command.
Who is the Tandem PM Operating Kit designed for?▼
It targets founders, product managers, and developers working in Claude Code who want structured project management inside their repository. The kit enforces a hat protocol (Founder, PM, Dev/QA) so solo operators and small teams get disciplined planning, execution, and review without separate PM software.
How do I install and run the Tandem PM kit in my project?▼
Invoke /tandem:install or ask to set up the PM kit. The install skill wraps the canonical install.js script, materializing the folder tree, seed files, pm:* scripts, hooks, and Command Center dashboard. Afterwards, /tandem:session-start restores project context at each session opening.
What prerequisites does the Tandem kit require?▼
You need a Claude Code environment and a project repository where the kit can create its _00-Project-Management folder structure. Phase execution requires a clean working tree on the main branch, and parallel batch execution requires stories to be provably file-disjoint per ADR-0075's batch check.
How does the kit enforce quality gates on stories?▼
Stories cannot start without passing the Definition of Ready checklist via refine-backlog, and cannot close without passing the Definition of Done gate in close-out-story. Every story must ship with a paired testplan in the same response, and testplan failures automatically generate BUG files before reporting.