claude-autopm 1.23.2 → 1.24.2

package/README.md

@@ -157,7 +157,7 @@ claude --dangerously-skip-permissions .
 /pm:epic-sync epic-001-authentication.md
 
 # 4. Start working
-/pm:next-task
+/pm:next
 
 # 5. Complete and sync
 /pm:issue-close

package/autopm/.claude/agents/frameworks/e2e-test-engineer.md

@@ -27,12 +27,37 @@ Access E2E testing frameworks and patterns:
 - **Accessibility**: WCAG, axe-core, screen reader testing
 - **Performance**: Lighthouse, Web Vitals, performance testing
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/testing/playwright` - Playwright automation
 - `mcp://context7/testing/cypress` - Cypress E2E testing
 - `mcp://context7/testing/visual` - Visual regression testing
 - `mcp://context7/testing/accessibility` - Accessibility testing
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your E2E testing expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific E2E test framework and scenario guidance
+- Dependency and parallelization mapping
+- Test automation, visual regression, and accessibility testing considerations
+
 ## E2E Testing Methodology
 
 **MANDATORY**: Focus on scenario-driven and user journey validation for all E2E test cases:

package/autopm/.claude/agents/frameworks/nats-messaging-expert.md

@@ -27,9 +27,34 @@ Use this agent for NATS messaging system including pub/sub, request/reply, and q
 - **Patterns**: Request/reply, queue groups, wildcards
 - **Security**: TLS, authentication, authorization
 
-**Documentation Queries:**
-- `mcp://context7/nats/latest`
-- `mcp://context7/nats/jetstream`
+**Documentation Queries (Technical):**
+- `mcp://context7/nats/latest` - Core NATS documentation
+- `mcp://context7/nats/jetstream` - JetStream streaming platform
+
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your NATS messaging expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific NATS messaging pattern and JetStream guidance
+- Dependency and parallelization mapping
+- Pub/sub, clustering, and high availability considerations
 
 ## Core Expertise
 

package/autopm/.claude/agents/frameworks/react-frontend-engineer.md

@@ -34,11 +34,36 @@ Before starting any implementation, you have access to live documentation throug
 3. **Performance Updates**: Verify latest performance optimization techniques
 4. **Accessibility Standards**: Access current a11y patterns and WCAG guidelines
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/react/latest` - React documentation and patterns
 - `mcp://context7/nextjs/app-router` - Next.js App Router patterns
 - `mcp://context7/typescript/react` - TypeScript + React best practices
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your React expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific React implementation guidance
+- Dependency and parallelization mapping
+- Component architecture and state management considerations
+
 **Core Expertise:**
 
 1. **React Development**:

package/autopm/.claude/agents/frameworks/react-ui-expert.md

@@ -20,12 +20,37 @@ Before implementing any UI solution, access live documentation through context7:
 - **Design Systems**: Material Design, accessibility guidelines
 - **Styling**: CSS-in-JS, styled-components, emotion
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/react/mui` - Material-UI documentation
 - `mcp://context7/react/chakra-ui` - Chakra UI components
 - `mcp://context7/react/ant-design` - Ant Design system
 - `mcp://context7/react/patterns` - React design patterns
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your React UI expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific React UI framework implementation guidance
+- Dependency and parallelization mapping
+- Component design system and accessibility considerations
+
 ## Test-Driven Development (TDD) Methodology
 
 **MANDATORY**: Follow strict TDD principles for all React UI component development:

package/autopm/.claude/agents/frameworks/tailwindcss-expert.md

@@ -28,12 +28,37 @@ Access Tailwind CSS documentation through context7:
 - **UI Components**: Component patterns, design systems
 - **Performance**: PurgeCSS, optimization techniques
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/css/tailwind` - Tailwind CSS utilities
 - `mcp://context7/css/tailwind-config` - Configuration guide
 - `mcp://context7/css/tailwind-plugins` - Plugin ecosystem
 - `mcp://context7/css/responsive` - Responsive design patterns
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your TailwindCSS expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific TailwindCSS utility and design system guidance
+- Dependency and parallelization mapping
+- Responsive design and theme customization considerations
+
 ## When to Use This Agent
 
 ### ✅ PRIMARY Use Cases (Best Choice)

package/autopm/.claude/agents/frameworks/ux-design-expert.md

@@ -29,12 +29,36 @@ Access UX design and accessibility documentation:
 - **UX Patterns**: Navigation, forms, data visualization
 - **Tools**: Figma, Sketch, design tokens, component libraries
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/design/material` - Material Design guidelines
 - `mcp://context7/design/accessibility` - Accessibility standards
 - `mcp://context7/design/patterns` - UX design patterns
 - `mcp://context7/design/systems` - Design system principles
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your UX design expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific UX/UI design and accessibility guidance
+- Dependency and parallelization mapping
+- User research, interaction design, and accessibility compliance considerations
 
 ## Core Expertise
 

package/autopm/.claude/agents/languages/bash-scripting-expert.md

@@ -38,12 +38,37 @@ Before starting any implementation, you have access to live documentation throug
 4. **Performance Tips**: Get optimization techniques
 5. **Security Guidelines**: Access secure scripting practices
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/bash/latest` - Bash documentation
 - `mcp://context7/posix/shell` - POSIX shell standards
 - `mcp://context7/coreutils/latest` - GNU coreutils
 - `mcp://context7/bash/security` - Security best practices
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development (with bats for Bash)
+4. **Technology-Specific Details**: Leverage your Bash/scripting expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific shell scripting implementation guidance
+- Dependency and parallelization mapping
+- Security and portability considerations included
+
 ## Core Expertise
 
 ### Script Architecture

package/autopm/.claude/agents/languages/javascript-frontend-engineer.md

@@ -36,12 +36,37 @@ Before starting any implementation, you have access to live documentation throug
 3. **Browser Compatibility**: Verify feature support across target browsers
 4. **Performance Guidelines**: Access latest web performance optimization techniques
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/javascript/latest` - JavaScript documentation
 - `mcp://context7/typescript/latest` - TypeScript handbook
 - `mcp://context7/mdn/web-apis` - Browser API references
 - `mcp://context7/webpack/latest` - Webpack configuration
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your JavaScript/TypeScript expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific technical implementation guidance
+- Dependency and parallelization mapping
+- No vague descriptions or missing acceptance criteria
+
 ## Core Expertise
 
 ### JavaScript Mastery

package/autopm/.claude/agents/languages/nodejs-backend-engineer.md

@@ -29,7 +29,7 @@ Before starting any implementation, you have access to live documentation throug
 - **Database Drivers**: MongoDB, PostgreSQL, MySQL documentation
 - **Security Guidelines**: OWASP Node.js security cheatsheet
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 
 - `mcp://context7/nodejs/latest` - Node.js documentation
 - `mcp://context7/express/latest` - Express framework
@@ -38,6 +38,13 @@ Before starting any implementation, you have access to live documentation throug
 - `mcp://context7/fastify/latest` - Fastify framework
 - `mcp://context7/typescript/node` - TypeScript for Node.js
 
+**Documentation Queries (Task Creation):**
+
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
 ### Documentation Retrieval Protocol
 
 1. **Check Framework Docs**: Query context7 for specific framework patterns
@@ -45,6 +52,25 @@ Before starting any implementation, you have access to live documentation throug
 3. **Security Standards**: Access current security recommendations
 4. **Performance Patterns**: Get latest Node.js optimization techniques
 
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your Node.js/backend expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific technical implementation guidance for backend/APIs
+- Dependency and parallelization mapping
+- Security and performance considerations included
+
 ## Core Expertise
 
 ### Node.js Mastery

package/autopm/.claude/agents/languages/python-backend-engineer.md

@@ -34,11 +34,36 @@ Before starting any implementation, you have access to live documentation throug
 3. **Security Updates**: Verify latest security recommendations for authentication and data handling
 4. **Performance Patterns**: Access latest async patterns and optimization techniques
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/fastapi/latest` - FastAPI documentation
-- `mcp://context7/sqlalchemy/2.0` - SQLAlchemy 2.0 async patterns  
+- `mcp://context7/sqlalchemy/2.0` - SQLAlchemy 2.0 async patterns
 - `mcp://context7/pydantic/v2` - Pydantic v2 validation patterns
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your Python backend expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific Python/FastAPI implementation guidance
+- Dependency and parallelization mapping
+- API design, database integration, and async pattern considerations
+
 **Core Expertise:**
 
 1. **FastAPI Development**:

package/autopm/.claude/agents/languages/python-backend-expert.md

@@ -20,12 +20,37 @@ Before implementing any Python backend solution, access live documentation throu
 - **Testing**: pytest, unittest, mock, coverage tools
 - **Async**: asyncio, aiohttp, uvloop, concurrent.futures
 
-**Documentation Queries:**
+**Documentation Queries (Technical):**
 - `mcp://context7/python/fastapi` - FastAPI framework
 - `mcp://context7/python/sqlalchemy` - SQLAlchemy ORM
 - `mcp://context7/python/django` - Django framework
 - `mcp://context7/python/pytest` - pytest testing
 
+**Documentation Queries (Task Creation):**
+- `mcp://context7/agile/task-breakdown` - Task decomposition patterns
+- `mcp://context7/agile/user-stories` - INVEST criteria for tasks
+- `mcp://context7/agile/acceptance-criteria` - Writing effective AC
+- `mcp://context7/project-management/estimation` - Effort estimation
+
+## Task Creation Excellence
+
+When creating implementation tasks (for epic decomposition or project planning):
+
+1. **Query Context7 First**: Access latest agile/PM best practices
+2. **Follow INVEST Criteria**: Tasks must be Independent, Negotiable, Valuable, Estimable, Small, Testable
+3. **Include TDD Requirements**: Every task must enforce Test-Driven Development
+4. **Technology-Specific Details**: Leverage your Python backend expertise in technical details
+5. **Clear Acceptance Criteria**: Specific, measurable, testable criteria
+
+**Task Structure Template**: Use frontmatter with name, status, created, depends_on, parallel, conflicts_with. Include sections for Description, TDD Requirements, Acceptance Criteria, Technical Details, Dependencies, Effort Estimate, Definition of Done.
+
+**Quality Standards**:
+- Tasks completable in 1-3 days maximum
+- Action-oriented titles (verb + noun)
+- Specific Python framework implementation guidance
+- Dependency and parallelization mapping
+- Architecture patterns, ORM integration, and async support considerations
+
 ## Test-Driven Development (TDD) Methodology
 
 **MANDATORY**: Follow strict TDD principles for all backend development:

package/autopm/.claude/commands/pm/context-create.md

@@ -0,0 +1,136 @@
+---
+allowed-tools: Bash, Read, Write, Glob
+---
+
+# Context Create
+
+Initialize project context documentation for AI agent memory.
+
+## Required Documentation Access
+
+**MANDATORY:** Before creating context, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/documentation/project-context` - Project documentation standards
+- `mcp://context7/agile/project-setup` - Project initialization best practices
+- `mcp://context7/knowledge-management/technical-documentation` - Documentation organization patterns
+
+**Why This is Required:**
+- Ensures context follows industry standards
+- Provides templates aligned with best practices
+- Establishes effective knowledge management patterns
+
+## Instructions
+
+Create comprehensive project context in `.claude/context/` directory.
+
+### 1. Check if context already exists
+
+```bash
+if [ -d ".claude/context" ]; then
+  echo "⚠️  Context already exists. Use /pm:context-update to modify."
+  exit 1
+fi
+```
+
+### 2. Create context directory structure
+
+```bash
+mkdir -p .claude/context
+```
+
+### 3. Copy and customize templates
+
+**Read templates from AutoPM installation:**
+- `.claude/templates/context-templates/project-brief.md.template`
+- `.claude/templates/context-templates/tech-context.md.template`
+- `.claude/templates/context-templates/progress.md.template`
+- `.claude/templates/context-templates/project-structure.md.template`
+
+### 4. Auto-populate with project information
+
+**Analyze project and pre-fill templates:**
+
+1. **Read package.json** for tech stack:
+   - Extract dependencies and devDependencies
+   - Determine Node.js version from engines
+   - Identify testing framework (Jest, Mocha, etc.)
+   - Detect package manager from lock files
+
+2. **Read README.md** for project description:
+   - Extract project name and description
+   - Identify key features and objectives
+   - Find usage examples
+
+3. **Detect directory structure:**
+   - Scan top-level directories
+   - Identify common patterns (src/, test/, docs/, etc.)
+   - Map key configuration files
+
+4. **Initialize progress:**
+   - Set initial phase as "Setup" or "Development"
+   - Mark context creation as first completed task
+   - Set progress to appropriate starting percentage
+
+### 5. Create context README
+
+Write `.claude/context/README.md`:
+
+```markdown
+# Project Context
+
+This directory maintains comprehensive project information for AI agents.
+
+## Files
+- **project-brief.md**: Project scope and objectives
+- **tech-context.md**: Technology stack and dependencies
+- **progress.md**: Current status and next steps
+- **project-structure.md**: Directory layout and key files
+
+## Usage
+- `/pm:context-prime`: Load context for new session
+- `/pm:context-update`: Update after changes
+- `/pm:context`: View current context
+
+## Maintenance
+Keep these files updated as the project evolves. Run `/pm:context-update` after:
+- Adding new dependencies
+- Completing major tasks
+- Changing project structure
+- Updating technical stack
+```
+
+### 6. Write populated templates
+
+Create the following files in `.claude/context/`:
+- `project-brief.md` (populated from README and package.json)
+- `tech-context.md` (populated from package.json and file detection)
+- `progress.md` (initialized with setup phase)
+- `project-structure.md` (populated from directory scan)
+
+### 7. Confirm creation
+
+Display success message:
+
+```
+✅ Context created in .claude/context/
+
+📝 Files created:
+   - project-brief.md (auto-populated from README)
+   - tech-context.md (auto-populated from package.json)
+   - progress.md (initialized)
+   - project-structure.md (auto-populated from directory scan)
+   - README.md (usage guide)
+
+💡 Next steps:
+   1. Review and customize the context files
+   2. Run /pm:context-prime to load context into session
+   3. Update regularly with /pm:context-update
+```
+
+## Output Format
+
+Return a structured summary of:
+- Files created with auto-populated content preview
+- Any information that couldn't be auto-detected
+- Recommendations for manual customization