docs: sync KB — pd-plan-release-1.0.0.md
All checks were successful
Reindex Knowledge Base / reindex (push) Successful in 4s

This commit is contained in:
Cal Corum 2026-03-23 02:00:43 -05:00
parent b2117416f6
commit cfde1c4d0c

View File

@ -0,0 +1,57 @@
---
title: "pd-plan CLI Release — 1.0.0"
description: "Initial release of the Paper Dynasty initiative tracker — a local SQLite CLI for cross-project priority management."
type: reference
domain: paper-dynasty
tags: [release-notes, pd-plan, infrastructure, paper-dynasty]
---
# pd-plan CLI Release — 1.0.0
**Date:** 2026-03-23
**Version:** 1.0.0
**Install location:** `~/.claude/skills/paper-dynasty/plan/`
**Database:** `~/.claude/skills/paper-dynasty/plan/initiatives.db`
**Install method:** `pip install -e . --user` (editable install, `pd-plan` available system-wide)
## Release Summary
Initial release of `pd-plan`, a zero-dependency SQLite-backed CLI for tracking Paper Dynasty cross-project initiatives. Designed for PO agents and session startup to quickly understand current priorities, track progress, and coordinate work across all PD repos.
## Features
### Commands
- **`pd-plan summary`** — Dashboard view showing phase progress, top priorities, and recent activity. Intended for session startup.
- **`pd-plan list`** — Tabular view of initiatives with filters: `--phase`, `--status`, `--impact`, `--repo`, `--owner`, `--all`
- **`pd-plan next`** — Returns the highest-priority non-blocked initiative. Supports `--repo` and `--owner` filters.
- **`pd-plan show [id]`** — Full details of an initiative including description, linked issues, and activity log.
- **`pd-plan add [title]`** — Create a new initiative with `--phase`, `--priority`, `--impact`, `--size`, `--repos`, `--linked`, `--description`
- **`pd-plan update [id]`** — Update fields: `--status`, `--priority`, `--owner`, `--blocked-by`, `--link`, `--note`
- **`pd-plan done [id]`** — Shortcut for `--status done`
- **`pd-plan seed`** — Populate database with initial initiatives from the ROADMAP (idempotent)
### Cross-cutting
- `--json` flag on all commands for machine-readable output
- `--actor` flag for attribution in the activity log (e.g., `--actor pd-ops`)
- Auto-creates database on first run
- Activity log tracks all status changes and notes with timestamps
### Schema
- **`initiatives`** table: id, title, description, phase (1-3), status (backlog/active/in_progress/blocked/done), priority (1-100), impact (retention/acquisition/engagement), size (S/M/L/XL), repos, linked_issues, blocked_by, owner, notes, timestamps
- **`activity_log`** table: initiative_id, action, old/new values, actor, timestamp
### Seed Data
17 initiatives across 3 phases, sourced from `ROADMAP.md`:
- Phase 1 (Foundation): 8 initiatives — Refractor system, backlog clearance, API stability, SQLite cleanup, ruff resolution
- Phase 2 (Engagement): 5 initiatives — pack experience, leagues, content pipeline, social features, gauntlets
- Phase 3 (Growth): 4 initiatives — website, web app, onboarding, analytics
## Integration
- Referenced in parent `CLAUDE.md` as session startup instruction
- Documented in `/paper-dynasty` skill under "Initiative Tracker" section
- All 5 PO/ops agents (`pd-database`, `pd-discord`, `pd-cards`, `pd-growth`, `pd-ops`) have `pd-plan` instructions in their agent definitions
## Dependencies
None — pure Python stdlib (sqlite3, argparse, textwrap, json, datetime).