claude-autopm 1.10.3 → 1.10.4

package/autopm/.claude/commands/pm/issue-show.md

@@ -13,79 +13,12 @@ Display issue and sub-issues with detailed information.
 
 ## Instructions
 
-You are displaying comprehensive information about a GitHub issue and related sub-issues for: **Issue #$ARGUMENTS**
-
-### 1. Fetch Issue Data
-- Use `gh issue view #$ARGUMENTS` to get GitHub issue details
-- Look for local task file: first check `.claude/epics/*/$ARGUMENTS.md` (new naming)
-- If not found, search for file with `github:.*issues/$ARGUMENTS` in frontmatter (old naming)
-- Check for related issues and sub-tasks
-
-### 2. Issue Overview
-Display issue header:
-```
-🎫 Issue #$ARGUMENTS: {Issue Title}
-   Status: {open/closed}
-   Labels: {labels}
-   Assignee: {assignee}
-   Created: {creation_date}
-   Updated: {last_update}
-   
-📝 Description:
-{issue_description}
-```
-
-### 3. Local File Mapping
-If local task file exists:
-```
-📁 Local Files:
-   Task file: .claude/epics/{epic_name}/{task_file}
-   Updates: .claude/epics/{epic_name}/updates/$ARGUMENTS/
-   Last local update: {timestamp}
-```
-
-### 4. Sub-Issues and Dependencies
-Show related issues:
-```
-🔗 Related Issues:
-   Parent Epic: #{epic_issue_number}
-   Dependencies: #{dep1}, #{dep2}
-   Blocking: #{blocked1}, #{blocked2}
-   Sub-tasks: #{sub1}, #{sub2}
-```
-
-### 5. Recent Activity
-Display recent comments and updates:
-```
-💬 Recent Activity:
-   {timestamp} - {author}: {comment_preview}
-   {timestamp} - {author}: {comment_preview}
-   
-   View full thread: gh issue view #$ARGUMENTS --comments
-```
-
-### 6. Progress Tracking
-If task file exists, show progress:
-```
-✅ Acceptance Criteria:
-   ✅ Criterion 1 (completed)
-   🔄 Criterion 2 (in progress)
-   ⏸️ Criterion 3 (blocked)
-   □ Criterion 4 (not started)
-```
-
-### 7. Quick Actions
-```
-🚀 Quick Actions:
-   Start work: /pm:issue-start $ARGUMENTS
-   Sync updates: /pm:issue-sync $ARGUMENTS
-   Add comment: gh issue comment #$ARGUMENTS --body "your comment"
-   View in browser: gh issue view #$ARGUMENTS --web
-```
-
-### 8. Error Handling
-- Handle invalid issue numbers gracefully
-- Check for network/authentication issues
-- Provide helpful error messages and alternatives
-
-Provide comprehensive issue information to help developers understand context and current status for Issue #$ARGUMENTS.
+Run `node .claude/scripts/pm/issue-show.js $ARGUMENTS` using the Bash tool and show me the complete output.
+
+This will display comprehensive information about the GitHub issue including:
+1. Issue details and status
+2. Local file mappings and task files
+3. Sub-issues and dependencies
+4. Recent activity and comments
+5. Progress tracking with acceptance criteria
+6. Quick action suggestions

package/autopm/.claude/commands/pm/prd-parse.md

@@ -11,165 +11,15 @@ Convert PRD to technical implementation epic.
 /pm:prd-parse <feature_name>
 ```
 
-## Required Rules
-
-**IMPORTANT:** Before executing this command, read and follow:
-- `.claude/rules/datetime.md` - For getting real current date/time
-
-## Preflight Checklist
-
-Before proceeding, complete these validation steps.
-Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.
-
-### Validation Steps
-1. **Verify <feature_name> was provided as a parameter:**
-   - If not, tell user: "❌ <feature_name> was not provided as parameter. Please run: /pm:prd-parse <feature_name>"
-   - Stop execution if <feature_name> was not provided
-
-2. **Verify PRD exists:**
-   - Check if `.claude/prds/$ARGUMENTS.md` exists
-   - If not found, tell user: "❌ PRD not found: $ARGUMENTS. First create it with: /pm:prd-new $ARGUMENTS"
-   - Stop execution if PRD doesn't exist
-
-3. **Validate PRD frontmatter:**
-   - Verify PRD has valid frontmatter with: name, description, status, created
-   - If frontmatter is invalid or missing, tell user: "❌ Invalid PRD frontmatter. Please check: .claude/prds/$ARGUMENTS.md"
-   - Show what's missing or invalid
-
-4. **Check for existing epic:**
-   - Check if `.claude/epics/$ARGUMENTS/epic.md` already exists
-   - If it exists, ask user: "⚠️ Epic '$ARGUMENTS' already exists. Overwrite? (yes/no)"
-   - Only proceed with explicit 'yes' confirmation
-   - If user says no, suggest: "View existing epic with: /pm:epic-show $ARGUMENTS"
-
-5. **Verify directory permissions:**
-   - Ensure `.claude/epics/` directory exists or can be created
-   - If cannot create, tell user: "❌ Cannot create epic directory. Please check permissions."
-
 ## Instructions
 
-You are a technical lead converting a Product Requirements Document into a detailed implementation epic for: **$ARGUMENTS**
-
-### 1. Read the PRD
-- Load the PRD from `.claude/prds/$ARGUMENTS.md`
-- Analyze all requirements and constraints
-- Understand the user stories and success criteria
-- Extract the PRD description from frontmatter
-
-### 2. Technical Analysis
-- Identify architectural decisions needed
-- Determine technology stack and approaches
-- Map functional requirements to technical components
-- Identify integration points and dependencies
-
-### 3. File Format with Frontmatter
-Create the epic file at: `.claude/epics/$ARGUMENTS/epic.md` with this exact structure:
-
-```markdown
----
-name: $ARGUMENTS
-status: backlog
-created: [Current ISO date/time]
-progress: 0%
-prd: .claude/prds/$ARGUMENTS.md
-github: [Will be updated when synced to GitHub]
----
-
-# Epic: $ARGUMENTS
-
-## Overview
-Brief technical summary of the implementation approach
-
-## Architecture Decisions
-- Key technical decisions and rationale
-- Technology choices
-- Design patterns to use
-
-## Technical Approach
-### Frontend Components
-- UI components needed
-- State management approach
-- User interaction patterns
-
-### Backend Services
-- API endpoints required
-- Data models and schema
-- Business logic components
-
-### Infrastructure
-- Deployment considerations
-- Scaling requirements
-- Monitoring and observability
-
-## Implementation Strategy
-- Development phases
-- Risk mitigation
-- Testing approach
-
-## Task Breakdown Preview
-High-level task categories that will be created:
-- [ ] Category 1: Description
-- [ ] Category 2: Description
-- [ ] etc.
-
-## Dependencies
-- External service dependencies
-- Internal team dependencies
-- Prerequisite work
-
-## Success Criteria (Technical)
-- Performance benchmarks
-- Quality gates
-- Acceptance criteria
-
-## Estimated Effort
-- Overall timeline estimate
-- Resource requirements
-- Critical path items
-```
-
-### 4. Frontmatter Guidelines
-- **name**: Use the exact feature name (same as $ARGUMENTS)
-- **status**: Always start with "backlog" for new epics
-- **created**: Get REAL current datetime by running: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-- **progress**: Always start with "0%" for new epics
-- **prd**: Reference the source PRD file path
-- **github**: Leave placeholder text - will be updated during sync
-
-### 5. Output Location
-Create the directory structure if it doesn't exist:
-- `.claude/epics/$ARGUMENTS/` (directory)
-- `.claude/epics/$ARGUMENTS/epic.md` (epic file)
-
-### 6. Quality Validation
-
-Before saving the epic, verify:
-- [ ] All PRD requirements are addressed in the technical approach
-- [ ] Task breakdown categories cover all implementation areas
-- [ ] Dependencies are technically accurate
-- [ ] Effort estimates are realistic
-- [ ] Architecture decisions are justified
-
-### 7. Post-Creation
-
-After successfully creating the epic:
-1. Confirm: "✅ Epic created: .claude/epics/$ARGUMENTS/epic.md"
-2. Show summary of:
-   - Number of task categories identified
-   - Key architecture decisions
-   - Estimated effort
-3. Suggest next step: "Ready to break down into tasks? Run: /pm:epic-decompose $ARGUMENTS"
-
-## Error Recovery
-
-If any step fails:
-- Clearly explain what went wrong
-- If PRD is incomplete, list specific missing sections
-- If technical approach is unclear, identify what needs clarification
-- Never create an epic with incomplete information
+Run `node .claude/scripts/pm/prd-parse.js $ARGUMENTS` using the Bash tool and show me the complete output.
 
-Focus on creating a technically sound implementation plan that addresses all PRD requirements while being practical and achievable for "$ARGUMENTS".
+This will convert the Product Requirements Document into a detailed technical implementation epic including:
+1. Technical analysis and architecture decisions
+2. Implementation strategy and phases
+3. Task breakdown preview (limited to 10 or fewer tasks)
+4. Dependencies and success criteria
+5. Effort estimates and timeline
 
-## IMPORTANT:
-- Aim for as few tasks as possible and limit the total number of tasks to 10 or less.
-- When creating the epic, identify ways to simplify and improve it. Look for ways to leverage existing functionality instead of creating more code when possible.
+The script handles all validation, reads the PRD file, and creates the epic structure at `.claude/epics/$ARGUMENTS/epic.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-autopm",
-  "version": "1.10.3",
+  "version": "1.10.4",
   "description": "Autonomous Project Management Framework for Claude Code - Advanced AI-powered development automation",
   "main": "bin/autopm.js",
   "bin": {