pm-architect
Expert project manager orchestrating backlog-curator, work-delegator, workstream-coordinator, and roadmap-strategist sub-skills. Coordinates complex software projects through delegation and strategic oversight. Activates when managing projects, coordinating work, or tracking overall progress.
SKILL.md
| Name | pm-architect |
| Description | Expert project manager orchestrating backlog-curator, work-delegator, workstream-coordinator, and roadmap-strategist sub-skills. Coordinates complex software projects through delegation and strategic oversight. Activates when managing projects, coordinating work, or tracking overall progress. |
PM Architect Default Configuration
This directory contains default configuration for the PM (Project Manager) Architect agent, which orchestrates development workflows and manages project execution.
Overview
The PM Architect is a specialized agent that acts as a project manager, understanding user preferences and work patterns to provide intelligent project management and workflow orchestration.
Configuration File
defaults.yaml
Generated from comprehensive analysis of 1,205 user messages across 15 recent sessions (Oct-Nov 2025), this configuration file captures:
- User Profile: Work style, autonomy preferences, quality emphasis
- Scope Preferences: Default to complete implementations (255:1 ratio)
- Autonomy Settings: When to proceed vs. when to checkpoint
- Quality Gates: Required verification and testing
- Work Organization: PR separation strategies, phase management
- Communication Style: Polite but firm, specific references
- Workflow Adherence: Strict workflow compliance
Data-Driven Calibration
This configuration is based on statistical analysis of actual usage patterns:
- Source: Claude-trace logs from 15 sessions
- Sample Size: 1,205 user messages
- Confidence: High (100+ observations per pattern)
- Coverage: October-November 2025
Key Patterns Identified
- Completeness First (255:1 ratio) - Strong preference for complete implementations
- Quality Always (888 instances) - Quality verification expected by default
- High Autonomy (2.2:1 ratio) - Proceed independently with architectural checkpoints
- Phase Separation (6 instances) - Keep features/phases in separate PRs
- Polite but Firm (550/124) - Match polite tone but respect firm boundaries
Usage
The PM Architect agent automatically loads these defaults when invoked. The configuration informs:
- Default scope selection (complete vs. minimal)
- When to ask for permission vs. proceed autonomously
- Required quality gates and verification steps
- PR organization and phase management strategies
- Communication style and status reporting
Related Documentation
- Analysis Report: Issue #1504
- Full Analysis:
.claude/runtime/README_TRACE_ANALYSIS.md - User Preferences:
.claude/context/USER_PREFERENCES.md - Workflow:
.claude/workflow/DEFAULT_WORKFLOW.md
Maintenance
- Version: 1.0
- Generated: 2025-11-22
- Next Review: 2025-12-22
- Update Strategy: Re-analyze monthly to detect pattern evolution
Philosophy Alignment
This configuration follows amplihack's core principles:
- Ruthless Simplicity: Single YAML file, clear structure
- Data-Driven: Based on actual usage patterns, not assumptions
- Zero-BS: No placeholders, all patterns statistically validated
- Modular Design: Self-contained configuration, clear purpose