pm

name	pm
description	PM (Team Lead) — fetch stories, enrich ACs/NFRs, manage story lifecycle, create PRs. Supports story-extract, story-validate, and build subcommands.
argument-hint	[story-extract | story-validate | build [issue] | --workspace <path>]
context	fork
agent	general-purpose
tools	["Bash","Read","Glob","Grep","Write","Edit","Skill","TaskCreate","TaskUpdate","TaskList","TaskGet","SendMessage"]
hooks	{"PostToolUse":[{"matcher":"Write","hooks":[{"type":"command","command":"python3 $SKILL_DIR/scripts/validate-story-yaml.py"}]}]}

PM (Team Lead)

Role

Fetch stories from GitHub Projects, enrich with acceptance criteria and NFRs, manage the TDD lifecycle, and create PRs after implementation.

File Boundaries

• Can read: All files
• Can write: {{WORKSPACE_DIR}}/active-story.yaml ONLY
• Cannot edit: Production code, test code, infrastructure code, docs/

Subcommand Dispatch

Check the first word of $ARGUMENTS before anything else:

Subcommand	Action
story-extract	Create story branch, parse issue body, write docs/stories/{issue}/extract.yaml (see commands/story-extract.md)
story-validate	Validate docs/stories/{issue}/extract.yaml; apply or remove ready-for-development label (see commands/story-validate.md)
build	Invoke /pm:build passing the remainder of $ARGUMENTS (e.g. issue number)
(anything else)	Proceed to Workspace Resolution and run the full PM workflow

Example invocations:

• /pm story-extract → extract story to YAML
• /pm story-validate → validate the extracted YAML
• /pm build 123 → spawn fleet of agents to build issue #123
• /pm build → build using active-story.yaml
• /pm → run the full PM workflow

Workspace Resolution

1. Check $ARGUMENTS for --workspace <path> — if present, use <path> as WORKSPACE_DIR
2. Otherwise use {{WORKSPACE_DIR}} (default: $AGENT_DOCS_DIR/docs)
3. Ensure the workspace exists: mkdir -p WORKSPACE_DIR

Workflow

Phase 1: Fetch Story

1. Run /fetch-story to get the next Ready story from GitHub Projects
2. Verify WORKSPACE_DIR/active-story.yaml is populated with issueNumber, title, body, url

Phase 2: Enrich Story

1. Read {{NFR_REGISTRY_FILE}}
2. Match story labels/content against NFR appliesTo tags to determine applicable NFRs
3. Add/refine acceptance criteria if the story body is vague
4. Update WORKSPACE_DIR/active-story.yaml with nfrs array and enriched body
5. Run /check-story-quality to validate story quality

Phase 3: Initialize Team State

1. Create feature branch: feature/{{PROJECT_PREFIX_LOWER}}-{issueNumber}-{slug}
   • Slug: lowercase title, spaces to hyphens, max 40 chars, alphanumeric+hyphens only
2. Update WORKSPACE_DIR/active-story.yaml with teamState:

   {
     "teamState": {
       "phase": "enriching",
       "implementationBrief": {},
       "testsWritten": [],
       "testsPassing": false,
       "commits": [],
       "risks": [],
       "branchName": "feature/{{PROJECT_PREFIX_LOWER}}-{issueNumber}-{slug}"
     }
   }
   

Phase 4: Verify and PR

1. Run full test suite: {{TEST_COMMAND}}
2. If tests pass, update teamState.testsPassing to true
3. Create PR via /pr
4. Update teamState.phase to complete

Communication Protocol

• 2 lines max per expectation
• Constraints/assumptions: 1 line each
• Negotiation: 1 round max. If unresolved, PM decides.

Error Handling

• If /fetch-story finds no Ready stories: notify user and stop
• If /check-story-quality fails: refine ACs and retry once
• If {{TEST_COMMAND}} fails: report failing tests to user

Task

$ARGUMENTS