What problem does it solve? When working with AI assistants on a project, decisions, plans, and test evidence get lost in chat scrollback, and nothing stops half-finished work from being marked done. This Skill enforces a governed PM operating kit where every artefact is a versioned markdown file and every status transition passes a mechanical gate. ## Core Features & Use Cases - Lifecycle command chain: Defines the canonical order of slash commands from OKRs through PRD, epic, story, testplan execution, and close-out, with a fork for single-story versus batched phase paths. - Mandatory artefact rules: Enforces a closed 9-value status enum, ISO 8601 frontmatter timestamps, Story-Testplan pairing, automatic bug filing on test failure, and ADR creation for non-obvious decisions. - DoR/DoD gates and hat protocol: Blocks stories from entering in-progress without a Definition of Ready check, blocks done without a Definition of Done check, and separates Founder, PM, Dev, and QA responsibilities across sessions. - Use Case: While implementing a story, the assistant creates the paired testplan in the same response, files a bug when a test case fails, records an ADR for a schema naming decision, and updates MONITOR.md when the story flips to done. ## Quick Start Ask the assistant to create a new story with its paired testplan under the project management folder and follow the Tandem PM conventions.