prjct-cli 1.22.0 → 1.24.0

package/templates/context/roadmap.md

@@ -1,221 +0,0 @@
----
-description: 'Template for generated roadmap context'
-generated-by: 'p. plan, p. sync'
-storage-source: 'storage/roadmap.json'
----
-
-# Roadmap Context Template
-
-This template defines the format for `{globalPath}/context/roadmap.md` generated by:
-- `p. plan` - After quarter planning
-- `p. sync` - After roadmap generation from git
-
----
-
-## Template
-
-```markdown
-# Roadmap
-
-**Last Updated:** {lastUpdated}
-
----
-
-## Strategy
-
-**Goal:** {strategy.goal}
-
-### Phases
-{FOR EACH phase in strategy.phases:}
-- **{phase.id}**: {phase.name} ({phase.status})
-{END FOR}
-
-### Success Metrics
-{FOR EACH metric in strategy.successMetrics:}
-- {metric}
-{END FOR}
-
----
-
-## Quarters
-
-{FOR EACH quarter in quarters:}
-### {quarter.id}: {quarter.name}
-
-**Status:** {quarter.status}
-**Theme:** {quarter.theme}
-**Capacity:** {capacity.allocatedHours}/{capacity.totalHours}h ({utilization}%)
-
-#### Goals
-{FOR EACH goal in quarter.goals:}
-- {goal}
-{END FOR}
-
-#### Features
-{FOR EACH featureId in quarter.features:}
-- [{status icon}] **{feature.name}** ({feature.status}, {feature.progress}%)
-  - PRD: {feature.prdId || 'None (legacy)'}
-  - Estimated: {feature.effortTracking?.estimated?.hours || '?'}h
-  - Value Score: {feature.valueScore || 'N/A'}
-  - Dependencies: {feature.dependencies?.join(', ') || 'None'}
-{END FOR}
-
-{END FOR}
-
----
-
-## Active Work
-
-{FOR EACH feature WHERE status == 'active':}
-### {feature.name}
-
-| Attribute | Value |
-|-----------|-------|
-| Progress | {feature.progress}% |
-| Branch | {feature.branch || 'N/A'} |
-| Quarter | {feature.quarter || 'Unassigned'} |
-| PRD | {feature.prdId || 'Legacy (no PRD)'} |
-| Started | {feature.createdAt} |
-
-#### Tasks
-{FOR EACH task in feature.tasks:}
-- [{task.completed ? 'x' : ' '}] {task.description}
-{END FOR}
-
-{END FOR}
-
----
-
-## Completed Features
-
-{FOR EACH feature WHERE status == 'completed' OR status == 'shipped':}
-- **{feature.name}** (v{feature.version || 'N/A'})
-  - Shipped: {feature.shippedAt || feature.completedDate}
-  - Actual: {feature.effortTracking?.actual?.hours || '?'}h vs Est: {feature.effortTracking?.estimated?.hours || '?'}h
-{END FOR}
-
----
-
-## Backlog
-
-Priority-ordered list of unscheduled items:
-
-| Priority | Item | Value | Effort | Score |
-|----------|------|-------|--------|-------|
-{FOR EACH item in backlog:}
-| {rank} | {item.title} | {item.valueScore} | {item.effortEstimate}h | {priorityScore} |
-{END FOR}
-
----
-
-## Legacy Features
-
-Features detected from git history (no PRD required):
-
-{FOR EACH feature WHERE legacy == true:}
-- **{feature.name}**
-  - Inferred From: {feature.inferredFrom}
-  - Status: {feature.status}
-  - Commits: {feature.commits?.length || 0}
-{END FOR}
-
----
-
-## Dependencies
-
-```
-{FOR EACH feature WHERE dependencies?.length > 0:}
-{feature.name}
-{FOR EACH depId in feature.dependencies:}
-  └── {dependency.name}
-{END FOR}
-{END FOR}
-```
-
----
-
-## Metrics Summary
-
-| Metric | Value |
-|--------|-------|
-| Total Features | {features.length} |
-| Planned | {planned.length} |
-| Active | {active.length} |
-| Completed | {completed.length} |
-| Shipped | {shipped.length} |
-| Legacy | {legacy.length} |
-| PRD-Backed | {prdBacked.length} |
-| Backlog | {backlog.length} |
-
-### Capacity by Quarter
-
-| Quarter | Allocated | Total | Utilization |
-|---------|-----------|-------|-------------|
-{FOR EACH quarter in quarters:}
-| {quarter.id} | {capacity.allocatedHours}h | {capacity.totalHours}h | {utilization}% |
-{END FOR}
-
-### Effort Accuracy (Shipped Features)
-
-| Feature | Estimated | Actual | Variance |
-|---------|-----------|--------|----------|
-{FOR EACH feature WHERE status == 'shipped' AND effortTracking:}
-| {feature.name} | {estimated.hours}h | {actual.hours}h | {variance}% |
-{END FOR}
-
-**Average Variance:** {averageVariance}%
-
----
-
-*Generated by prjct-cli | https://prjct.app*
-```
-
----
-
-## Status Icons
-
-| Status | Icon |
-|--------|------|
-| planned | [ ] |
-| active | [~] |
-| completed | [x] |
-| shipped | [+] |
-
----
-
-## Variable Reference
-
-| Variable | Source | Description |
-|----------|--------|-------------|
-| `lastUpdated` | roadmap.lastUpdated | ISO timestamp |
-| `strategy` | roadmap.strategy | Strategy object |
-| `quarters` | roadmap.quarters | Array of quarters |
-| `features` | roadmap.features | Array of features |
-| `backlog` | roadmap.backlog | Array of backlog items |
-| `utilization` | Calculated | (allocated/total) * 100 |
-| `priorityScore` | Calculated | valueScore / (effort/10) |
-
----
-
-## Generation Rules
-
-1. **Quarters** - Show only `planned` and `active` quarters by default
-2. **Features** - Group by status (active first, then planned)
-3. **Backlog** - Sort by priority score (descending)
-4. **Legacy** - Always show separately to distinguish from PRD-backed
-5. **Dependencies** - Only show features with dependencies
-6. **Metrics** - Always include for dashboard views
-
----
-
-## Integration with Linear/Jira/Monday
-
-The context file maps to PM tool exports:
-
-| Context Section | Linear | Jira | Monday |
-|-----------------|--------|------|--------|
-| Quarters | Cycles | Sprints | Timelines |
-| Features | Issues | Stories | Items |
-| Backlog | Backlog | Backlog | Inbox |
-| Status | State | Status | Status |
-| Capacity | Estimates | Story Points | Time |

package/templates/cursor/commands/bug.md

@@ -1,8 +0,0 @@
-# /bug - Report a bug
-
-**ARGUMENTS**: {{args}}
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/bug.md`
-
-Pass the arguments as the bug description.

package/templates/cursor/commands/done.md

@@ -1,4 +0,0 @@
-# /done - Complete current subtask
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/done.md`

package/templates/cursor/commands/pause.md

@@ -1,6 +0,0 @@
-# /pause - Pause current task
-
-**ARGUMENTS**: {{args}}
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/pause.md`

package/templates/cursor/commands/resume.md

@@ -1,4 +0,0 @@
-# /resume - Resume paused task
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/resume.md`

package/templates/cursor/commands/ship.md

@@ -1,8 +0,0 @@
-# /ship - Ship feature with PR + version bump
-
-**ARGUMENTS**: {{args}}
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/ship.md`
-
-Pass the arguments as the feature name (optional).

package/templates/cursor/commands/sync.md

@@ -1,4 +0,0 @@
-# /sync - Analyze project
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/sync.md`

package/templates/cursor/commands/task.md

@@ -1,8 +0,0 @@
-# /task - Start a task
-
-**ARGUMENTS**: {{args}}
-
-Run `npm root -g` to get npm global root, then read and execute:
-`{npmRoot}/prjct-cli/templates/commands/task.md`
-
-Pass the arguments as the task description.

package/templates/cursor/p.md

@@ -1,29 +0,0 @@
-# p. Command Router for Cursor IDE
-
-**ARGUMENTS**: {{args}}
-
-## Instructions
-
-1. **Get npm root**: Run `npm root -g`
-2. **Parse arguments**: First word = `command`, rest = `commandArgs`
-3. **Read template**: `{npmRoot}/prjct-cli/templates/commands/{command}.md`
-4. **Execute**: Follow the template with `commandArgs` as input
-
-## Example
-
-If arguments = `task fix the login bug`:
-- command = `task`
-- commandArgs = `fix the login bug`
-- npm root → `/opt/homebrew/lib/node_modules`
-- Read: `/opt/homebrew/lib/node_modules/prjct-cli/templates/commands/task.md`
-- Execute template with: `fix the login bug`
-
-## Available Commands
-
-task, done, ship, sync, init, idea, dash, next, pause, resume, bug,
-linear, github, jira, monday, enrich, feature, prd, plan, review,
-merge, git, test, cleanup, design, analyze, history, update, spec
-
-## Action
-
-NOW run `npm root -g` and read the appropriate command template.

package/templates/cursor/router.mdc

@@ -1,28 +0,0 @@
----
-description: "prjct - Context layer for AI coding agents"
-alwaysApply: true
----
-
-# prjct
-
-You are using **prjct**, a context layer for AI coding agents.
-
-## Load Full Instructions
-
-1. Run: `npm root -g` to get the npm global root
-2. Read: `{npmRoot}/prjct-cli/templates/global/CURSOR.mdc`
-3. Follow those instructions for ALL `/command` requests
-
-## Quick Reference
-
-| Command | Action |
-|---------|--------|
-| `/sync` | Analyze project, generate agents |
-| `/task "..."` | Start a task |
-| `/done` | Complete subtask |
-| `/ship` | Ship with PR + version |
-
-## Note
-
-This router auto-regenerates with `/sync` if deleted.
-Full instructions are in the npm package (always up-to-date).

package/templates/design/api.md

@@ -1,95 +0,0 @@
----
-name: api-design
-description: Design API endpoints and contracts
-allowed-tools: [Read, Glob, Grep]
----
-
-# API Design
-
-Design RESTful API endpoints for the given feature.
-
-## Input
-- Target: {{target}}
-- Requirements: {{requirements}}
-
-## Analysis Steps
-
-1. **Identify Resources**
-   - What entities are involved?
-   - What operations are needed?
-   - What relationships exist?
-
-2. **Review Existing APIs**
-   - Read existing route files
-   - Match naming conventions
-   - Use consistent patterns
-
-3. **Design Endpoints**
-   - RESTful resource naming
-   - Appropriate HTTP methods
-   - Request/response shapes
-
-4. **Define Validation**
-   - Input validation rules
-   - Error responses
-   - Edge cases
-
-## Output Format
-
-```markdown
-# API Design: {target}
-
-## Endpoints
-
-### GET /api/{resource}
-**Description**: List all resources
-
-**Query Parameters**:
-- `limit`: number (default: 20)
-- `offset`: number (default: 0)
-
-**Response** (200):
-```json
-{
-  "data": [...],
-  "total": 100,
-  "limit": 20,
-  "offset": 0
-}
-```
-
-### POST /api/{resource}
-**Description**: Create resource
-
-**Request Body**:
-```json
-{
-  "field": "value"
-}
-```
-
-**Response** (201):
-```json
-{
-  "id": "...",
-  "field": "value"
-}
-```
-
-**Errors**:
-- 400: Invalid input
-- 401: Unauthorized
-- 409: Conflict
-
-## Authentication
-- Method: Bearer token / API key
-- Required for: POST, PUT, DELETE
-
-## Rate Limiting
-- 100 requests/minute per user
-```
-
-## Guidelines
-- Follow REST conventions
-- Use consistent error format
-- Document all parameters

package/templates/design/architecture.md

@@ -1,77 +0,0 @@
----
-name: architecture-design
-description: Design system architecture
-allowed-tools: [Read, Glob, Grep]
----
-
-# Architecture Design
-
-Design the system architecture for the given requirements.
-
-## Input
-- Target: {{target}}
-- Requirements: {{requirements}}
-- Project context
-
-## Analysis Steps
-
-1. **Understand Requirements**
-   - What problem are we solving?
-   - What are the constraints?
-   - What scale do we need?
-
-2. **Review Existing Architecture**
-   - Read current codebase structure
-   - Identify existing patterns
-   - Note integration points
-
-3. **Design Components**
-   - Core modules and responsibilities
-   - Data flow between components
-   - External dependencies
-
-4. **Define Interfaces**
-   - API contracts
-   - Data structures
-   - Event/message formats
-
-## Output Format
-
-Generate markdown document:
-
-```markdown
-# Architecture: {target}
-
-## Overview
-Brief description of the architecture.
-
-## Components
-- **Component A**: Responsibility
-- **Component B**: Responsibility
-
-## Data Flow
-```
-[Diagram using ASCII or mermaid]
-```
-
-## Interfaces
-### API Endpoints
-- `GET /resource` - Description
-- `POST /resource` - Description
-
-### Data Models
-- `Model`: { field: type }
-
-## Dependencies
-- External service X
-- Library Y
-
-## Decisions
-- Decision 1: Rationale
-- Decision 2: Rationale
-```
-
-## Guidelines
-- Match existing project patterns
-- Keep it simple - avoid over-engineering
-- Document decisions and trade-offs

package/templates/design/component.md

@@ -1,89 +0,0 @@
----
-name: component-design
-description: Design UI/code component
-allowed-tools: [Read, Glob, Grep]
----
-
-# Component Design
-
-Design a reusable component for the given requirements.
-
-## Input
-- Target: {{target}}
-- Requirements: {{requirements}}
-
-## Analysis Steps
-
-1. **Understand Purpose**
-   - What does this component do?
-   - Where will it be used?
-   - What inputs/outputs?
-
-2. **Review Existing Components**
-   - Read similar components
-   - Match project patterns
-   - Use existing utilities
-
-3. **Design Interface**
-   - Props/parameters
-   - Events/callbacks
-   - State management
-
-4. **Plan Implementation**
-   - File structure
-   - Dependencies
-   - Testing approach
-
-## Output Format
-
-```markdown
-# Component: {ComponentName}
-
-## Purpose
-Brief description of what this component does.
-
-## Props/Interface
-| Prop | Type | Required | Default | Description |
-|------|------|----------|---------|-------------|
-| id | string | yes | - | Unique identifier |
-| onClick | function | no | - | Click handler |
-
-## State
-- `isLoading`: boolean - Loading state
-- `data`: array - Fetched data
-
-## Events
-- `onChange(value)`: Fired when value changes
-- `onSubmit(data)`: Fired on form submit
-
-## Usage Example
-```jsx
-<ComponentName
-  id="example"
-  onClick={handleClick}
-/>
-```
-
-## File Structure
-```
-components/
-└── ComponentName/
-    ├── index.js
-    ├── ComponentName.jsx
-    ├── ComponentName.test.js
-    └── styles.css
-```
-
-## Dependencies
-- Library X for Y
-- Utility Z
-
-## Testing
-- Unit tests for logic
-- Integration test for interactions
-```
-
-## Guidelines
-- Match project component patterns
-- Keep components focused
-- Document all props

package/templates/design/database.md

@@ -1,78 +0,0 @@
----
-name: database-design
-description: Design database schema
-allowed-tools: [Read, Glob, Grep]
----
-
-# Database Design
-
-Design database schema for the given requirements.
-
-## Input
-- Target: {{target}}
-- Requirements: {{requirements}}
-
-## Analysis Steps
-
-1. **Identify Entities**
-   - What data needs to be stored?
-   - What are the relationships?
-   - What queries will be common?
-
-2. **Review Existing Schema**
-   - Read current models/migrations
-   - Match naming conventions
-   - Use consistent patterns
-
-3. **Design Tables/Collections**
-   - Fields and types
-   - Indexes for queries
-   - Constraints and defaults
-
-4. **Plan Migrations**
-   - Order of operations
-   - Data transformations
-   - Rollback strategy
-
-## Output Format
-
-```markdown
-# Database Design: {target}
-
-## Entities
-
-### users
-| Column | Type | Constraints | Description |
-|--------|------|-------------|-------------|
-| id | uuid | PK | Unique identifier |
-| email | varchar(255) | UNIQUE, NOT NULL | User email |
-| created_at | timestamp | NOT NULL, DEFAULT now() | Creation time |
-
-### posts
-| Column | Type | Constraints | Description |
-|--------|------|-------------|-------------|
-| id | uuid | PK | Unique identifier |
-| user_id | uuid | FK(users.id) | Author reference |
-| title | varchar(255) | NOT NULL | Post title |
-
-## Relationships
-- users 1:N posts (one user has many posts)
-
-## Indexes
-- `users_email_idx` on users(email)
-- `posts_user_id_idx` on posts(user_id)
-
-## Migrations
-1. Create users table
-2. Create posts table with FK
-3. Add indexes
-
-## Queries (common)
-- Get user by email: `SELECT * FROM users WHERE email = ?`
-- Get user posts: `SELECT * FROM posts WHERE user_id = ?`
-```
-
-## Guidelines
-- Normalize appropriately
-- Add indexes for common queries
-- Document relationships clearly