domain-pm

Coordinates PG-sized decomposition of domain tasks using SuperPM-provided context logs and validates requirements and dependencies.

6|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill domain-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-pm
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/domain-pm
Command: npx skills add https://github.com/i-standard1/yamasaki --skill domain-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain PM coordinates the decomposition of cross-domain tasks into programmatic work units (PGs) and directs their implementation within the domains/[ドメイン名]/ directory, ensuring domain responsibilities and constraints are respected and that work stays aligned with overarching project plans.

Core Features & Use Cases

  • Validates domain boundaries by reading domains/[ドメイン名]/CLAUDE.md to understand domain responsibilities and constraints.
  • Consumes SuperPM-provided context logs (logs/context/pm_[domain]_*.md) to verify task lists, dependencies, interfaces, and execution order.
  • Orchestrates task decomposition, assignment to PGs, and execution sequencing, with safety checks and a path for error recovery.
  • Reports back to SuperPM with completion status and updated domain-level context.

Quick Start

Invoke domain-pm inside domains/[ドメイン名]/ to decompose the current task into PG units and coordinate implementation.

Frequently Asked Questions about domain-pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose domain-level tasks into programmatic work units for implementation?

To coordinate domain tasks, invoke domain-pm inside domains/[domain_name]/ to decompose the current task into PG units, validate dependencies against spec-map.yml, and direct execution sequencing.

How does domain management validate requirements alignment before implementation starts?

Domain management validates requirements by reading CLAUDE.md for domain constraints, verifying all REQ-IDs exist in spec-map.yml, and consuming SuperPM context logs to ensure proper interfaces and execution order.

Do I need SuperPM context logs to coordinate engineering workflow tasks?

Yes, consuming SuperPM context logs (logs/context/pm_[domain]_*.md) is required to verify task lists, dependencies, interfaces, and execution order before orchestrating task decomposition and PG assignments.

What happens if REQ-IDs are missing or misaligned in spec-map.yml during task decomposition?

When REQ-IDs are missing or misaligned in spec-map.yml during task decomposition, the system reports these discrepancies back to SuperPM to halt misaligned implementation within the domain directory.

Can I use domain task coordination to manage cross-domain dependencies and interfaces?

Yes, domain task coordination verifies cross-domain dependencies and interfaces by consuming SuperPM context logs, orchestrating execution sequencing while respecting domain boundaries defined in CLAUDE.md.