prjct-cli 1.22.0 → 1.24.0

package/templates/commands/skill.md

@@ -1,259 +0,0 @@
----
-allowed-tools: [Read, Glob, Bash]
-description: 'List, search, and invoke skills'
-timestamp-rule: 'None'
-architecture: 'Skill discovery, installation, and execution'
----
-
-# /p:skill - Skill Management
-
-List, search, install, and invoke reusable skills.
-
-## Usage
-
-```
-/p:skill                        # List all skills
-/p:skill list                   # List all skills
-/p:skill search <query>         # Search skills
-/p:skill show <id>              # Show skill details
-/p:skill invoke <id>            # Invoke a skill
-/p:skill add <source>           # Install skill from remote source
-/p:skill remove <name>          # Remove an installed skill
-/p:skill init <name>            # Scaffold a new skill
-/p:skill check                  # Check for available updates
-```
-
-## Flow
-
-### List Skills (`/p:skill` or `/p:skill list`)
-
-1. Load skills from all sources:
-   - Project: `.prjct/skills/*.md` and `.prjct/skills/*/SKILL.md`
-   - Provider: `~/.claude/skills/*/SKILL.md` and `~/.claude/skills/*.md`
-   - Global: `~/.prjct-cli/skills/*.md` and `~/.prjct-cli/skills/*/SKILL.md`
-   - Built-in: `templates/skills/*.md`
-
-2. Check lock file at `~/.prjct-cli/skills/.skill-lock.json` for source info
-
-3. Output grouped by source:
-
-```
-## Available Skills
-
-### Project Skills
-- **custom-deploy** - Deploy to staging server
-
-### Global Skills (Provider)
-- **frontend-design** - Create production-grade UIs [github: vercel-labs/skills]
-- **my-template** - Personal code template
-
-### Built-in Skills
-- **code-review** - Review code for quality
-- **refactor** - Refactor code structure
-```
-
-### Search Skills (`/p:skill search <query>`)
-
-1. Search skill names, descriptions, and tags
-2. Sort by relevance
-3. Output matches
-
-### Show Skill (`/p:skill show <id>`)
-
-1. Load skill by ID
-2. Display metadata and content
-3. If remotely installed, show source tracking info
-
-```
-## Skill: frontend-design
-
-**Description:** Create production-grade frontend interfaces
-**Source:** global (github: vercel-labs/skills)
-**Tags:** frontend, design, ui
-**Version:** 1.0.0
-**Installed:** 2026-01-28T12:00:00.000Z
-**SHA:** abc123
-
-### Content
-[Full skill prompt content]
-```
-
-### Invoke Skill (`/p:skill invoke <id>`)
-
-1. Load skill by ID
-2. Return skill content for execution
-3. The skill content becomes the prompt
-
-### Add Skill (`/p:skill add <source>`)
-
-Install skills from remote sources.
-
-**Supported source formats:**
-- `owner/repo` — Clone GitHub repo, install all discovered skills
-- `owner/repo@skill-name` — Install specific skill from GitHub repo
-- `./local-path` — Install from local directory
-
-**Install flow:**
-1. Parse source string
-2. For GitHub: `git clone --depth 1` to temp dir (60s timeout)
-3. Discover SKILL.md files (scans `*/SKILL.md` and `skills/*/SKILL.md`)
-4. Copy to `~/.claude/skills/{name}/SKILL.md` (ecosystem standard format)
-5. Add `_prjct` metadata block to frontmatter (sourceUrl, sha, installedAt)
-6. Update lock file at `~/.prjct-cli/skills/.skill-lock.json`
-7. Clean up temp dir
-
-**Example:**
-```
-p. skill add vercel-labs/skills
-p. skill add my-org/custom-skills@api-designer
-p. skill add ./my-local-skill
-```
-
-**Output:**
-```
-✅ Installed 3 skills from vercel-labs/skills
-
-- frontend-design → ~/.claude/skills/frontend-design/SKILL.md
-- find-skills → ~/.claude/skills/find-skills/SKILL.md
-- code-review → ~/.claude/skills/code-review/SKILL.md
-
-Lock file updated: ~/.prjct-cli/skills/.skill-lock.json
-```
-
-### Remove Skill (`/p:skill remove <name>`)
-
-1. Remove skill directory from `~/.claude/skills/{name}/`
-2. Also remove flat file if it exists (`~/.claude/skills/{name}.md`)
-3. Remove entry from lock file
-4. Confirm removal
-
-**Output:**
-```
-✅ Removed skill: frontend-design
-
-Deleted: ~/.claude/skills/frontend-design/
-Lock file updated.
-```
-
-### Init Skill (`/p:skill init <name>`)
-
-Scaffold a new skill in the project.
-
-1. Create `.prjct/skills/{name}/SKILL.md` with template frontmatter
-2. Open for editing
-
-**Template:**
-```markdown
----
-name: {name}
-description: TODO - describe what this skill does
-agent: general
-tags: []
-version: 1.0.0
-author: {detected-author}
----
-
-# {Name} Skill
-
-## Purpose
-
-Describe what this skill helps with.
-
-## Instructions
-
-Step-by-step instructions for the AI agent...
-```
-
-### Check Updates (`/p:skill check`)
-
-Compare lock file SHAs with remote repositories to detect available updates.
-
-1. Read lock file entries
-2. For each GitHub-sourced skill, run `git ls-remote` to get latest SHA
-3. Compare with stored SHA
-4. Report skills with available updates (no auto-update)
-
-**Output:**
-```
-## Skill Update Check
-
-- **frontend-design** (vercel-labs/skills) — Update available
-  Current: abc123 → Latest: def456
-- **code-review** (vercel-labs/skills) — Up to date
-- **my-local-skill** (local) — Skipped (local source)
-
-1 update available. Run `p. skill add <source>` to update.
-```
-
-## Skill File Format
-
-Skills are markdown files with frontmatter. Two formats are supported:
-
-### Subdirectory Format (Ecosystem Standard)
-```
-~/.claude/skills/my-skill/SKILL.md
-```
-
-### Flat Format (Legacy)
-```
-~/.claude/skills/my-skill.md
-```
-
-### Frontmatter Schema
-
-```markdown
----
-name: My Skill
-description: What the skill does
-agent: general
-tags: [tag1, tag2]
-version: 1.0.0
-author: Author Name
-category: development
-_prjct:
-  sourceUrl: https://github.com/owner/repo
-  sourceType: github
-  installedAt: 2026-01-28T12:00:00.000Z
-  sha: abc123
----
-
-# Skill Content
-
-The actual prompt/instructions...
-```
-
-## Creating Custom Skills
-
-### Project Skill (repo-specific)
-Create `.prjct/skills/my-skill/SKILL.md` or `.prjct/skills/my-skill.md`
-
-### Global Skill (all projects)
-Create `~/.claude/skills/my-skill/SKILL.md` or `~/.prjct-cli/skills/my-skill.md`
-
-## Lock File
-
-Installed skills are tracked in `~/.prjct-cli/skills/.skill-lock.json`:
-
-```json
-{
-  "version": 1,
-  "generatedAt": "2026-01-28T...",
-  "skills": {
-    "frontend-design": {
-      "name": "frontend-design",
-      "source": { "type": "github", "url": "vercel-labs/skills", "sha": "abc123" },
-      "installedAt": "2026-01-28T...",
-      "filePath": "~/.claude/skills/frontend-design/SKILL.md"
-    }
-  }
-}
-```
-
-## Output Format
-
-```
-## Skills ({count} total)
-
-### {source}
-- **{name}** ({id}): {description} [{sourceInfo}]
-```

package/templates/commands/spec.md

@@ -1,218 +0,0 @@
----
-allowed-tools: [Read, Write, Glob, GetTimestamp, GetDate]
-description: 'Spec-driven development for complex features'
-timestamp-rule: 'GetTimestamp() and GetDate() for ALL timestamps'
-think-triggers: [explore_to_edit, complex_analysis]
-architecture: 'Write-Through (JSON → MD → Events)'
-storage-layer: true
-source-of-truth: 'storage/specs.json'
-claude-context: 'context/specs/'
----
-
-# /p:spec - Spec-Driven Development
-
-Spec-Driven Development. Creates detailed specifications for complex features before implementation.
-
-## Architecture: Write-Through Pattern
-
-**Source of Truth**: `storage/specs.json`
-**Claude Context**: `context/specs/{slug}.md` (generated)
-
-## Think First
-
-Before creating spec, analyze:
-1. Is this feature complex enough for a spec? (auth, payments, migrations = yes)
-2. What are the key architectural decisions to make?
-3. Are there multiple valid approaches? Document tradeoffs.
-4. What questions should I ask the user before proceeding?
-
-## Context Variables
-- `{projectId}`: From `.prjct/prjct.config.json`
-- `{globalPath}`: `~/.prjct-cli/projects/{projectId}`
-- `{specsStoragePath}`: `{globalPath}/storage/specs.json`
-- `{specsContextPath}`: `{globalPath}/context/specs/`
-- `{queuePath}`: `{globalPath}/storage/queue.json`
-
-## Purpose
-
-For features that require:
-- Clear requirements before coding
-- Design decisions documented
-- Tasks broken into 20-30 min chunks
-- User approval before starting
-
-## Flow
-
-### No params: Show template
-```
-→ Interactive spec template
-→ Ask for feature name
-→ Guide through requirements
-```
-
-### With feature name: Create spec
-```
-/p:spec "Dark Mode"
-1. Analyze: Context, patterns, dependencies
-2. Propose: Requirements + Design + Tasks
-3. Write: `storage/specs.json` + generate `context/specs/{slug}.md`
-4. Ask: User approval
-5. On approve: Add tasks to `storage/queue.json`, start first
-```
-
-## Spec Structure
-
-```markdown
-# Feature Spec: {name}
-
-**Created**: {GetDate()}
-**Status**: PENDING_APPROVAL | APPROVED | IN_PROGRESS | COMPLETED
-
-## Requirements (User approves)
-- [ ] Requirement 1
-- [ ] Requirement 2
-- [ ] Requirement 3
-
-## Design (Claude proposes)
-- **Approach**: {architecture decision}
-- **Key decisions**: {list}
-- **Dependencies**: {existing code/libs}
-
-## Tasks (20-30min each)
-1. [ ] Task 1 (20m) - {description}
-2. [ ] Task 2 (25m) - {description}
-3. [ ] Task 3 (30m) - {description}
-
-**Total**: {n} tasks, ~{Xh}
-
-## Notes
-- {implementation notes}
-- {edge cases to consider}
-```
-
-## Storage Format
-
-### storage/specs.json
-```json
-{
-  "specs": [
-    {
-      "id": "{specId}",
-      "name": "{feature}",
-      "slug": "{feature-slug}",
-      "status": "PENDING_APPROVAL",
-      "requirements": [...],
-      "design": {...},
-      "tasks": [...],
-      "createdAt": "{timestamp}",
-      "approvedAt": null
-    }
-  ],
-  "lastUpdated": "{timestamp}"
-}
-```
-
-## Validation
-
-- Feature name required for creation
-- Spec must have at least 1 requirement
-- Each task should be 20-30 minutes
-- Check for existing spec with same name
-
-## Response
-
-### On creation:
-```
-📋 Spec: {feature}
-
-Requirements ({n}):
-{numbered_list}
-
-Design:
-→ {approach}
-→ {key_decision}
-
-Tasks ({n}, ~{total_time}):
-{numbered_list}
-
-APPROVE? (y/n/edit)
-```
-
-### On approval:
-```
-✅ Spec approved: {feature}
-→ {n} tasks added to queue
-→ Starting: {task_1}
-
-Use /p:done when complete
-```
-
-## Examples
-
-```
-/p:spec "User Authentication"
-→ Creates spec with OAuth/JWT decisions
-→ Breaks into: setup, login, logout, session, tests
-→ Estimates ~4h total
-
-/p:spec "Dark Mode"
-→ Creates spec with theme approach
-→ Breaks into: toggle, state, styles, persist, test
-→ Estimates ~3h total
-```
-
-## Decision Logging (absorbed from /p:decision)
-
-Specs now capture architectural decisions inline. When making design choices:
-
-### Decision Format
-
-```
-/p:spec "API Design"
-
-[During spec creation, capture decisions:]
-
-Decision: Use REST instead of GraphQL
-Reasoning: Simpler for this use case, team familiarity
-Alternatives: GraphQL, gRPC
-```
-
-### Storage
-
-Decisions are stored in the spec itself:
-```json
-{
-  "id": "{specId}",
-  "name": "{feature}",
-  "decisions": [
-    {
-      "id": "{decisionId}",
-      "decision": "Use REST instead of GraphQL",
-      "reasoning": "Simpler for this use case",
-      "alternatives": ["GraphQL", "gRPC"],
-      "createdAt": "{timestamp}"
-    }
-  ]
-}
-```
-
-### Response (with decisions)
-```
-📝 Decision logged: Use REST instead of GraphQL
-
-ID: {decisionId}
-Reasoning: Simpler for this use case
-Alternatives: GraphQL, gRPC
-
-This creates institutional memory to avoid:
-- Repeating the same debates
-- Forgetting why something was done a certain way
-- Making inconsistent choices
-```
-
-## Natural Language Support
-
-- "p. spec" → Interactive spec creation
-- "p. spec dark mode" → Create spec for dark mode
-- "p. design spec auth" → Create spec for auth
-- "p. decision use postgres" → Log decision (now part of spec)

package/templates/commands/status.md

@@ -1,207 +0,0 @@
----
-allowed-tools: [Read, Bash]
----
-
-# p. status
-
-Visual workflow status showing current position in the prjct lifecycle.
-
-## Step 1: Resolve Project Paths
-
-```bash
-# Get projectId from local config
-cat .prjct/prjct.config.json | grep -o '"projectId"[[:space:]]*:[[:space:]]*"[^"]*"' | cut -d'"' -f4
-```
-
-Set `globalPath = ~/.prjct-cli/projects/{projectId}`
-
-## Step 2: Read State and Context
-
-READ:
-- `{globalPath}/storage/state.json` → current task, paused, previous
-- `{globalPath}/storage/queue.json` → upcoming tasks
-- `{globalPath}/storage/shipped.json` → recent ships
-- `{globalPath}/project.json` → lastSync timestamp
-
-```bash
-# Get staleness info
-prjct status --json 2>/dev/null || echo '{"isStale": false}'
-```
-
-## Step 3: Determine Workflow Position
-
-Based on state.json, determine current position:
-
-```
-IF no currentTask AND no previousTask:
-  position = "ready"  # Ready to start (after sync)
-ELSE IF currentTask.status == "active":
-  position = "working"  # In task
-ELSE IF currentTask.status == "in_review":
-  position = "reviewing"  # PR open, waiting for merge
-ELSE IF currentTask.status == "shipped":
-  position = "shipped"  # Ready for next task
-ELSE:
-  position = "idle"
-```
-
-## Step 4: Calculate Progress
-
-```
-IF currentTask.subtasks exists:
-  completed = count where status == "completed"
-  total = subtasks.length
-  percent = (completed / total) * 100
-  progressBar = generateBar(percent, 10)  # 10 chars wide
-```
-
-Progress bar generation:
-```
-filled = floor(percent / 10)
-empty = 10 - filled
-bar = "█" × filled + "░" × empty
-```
-
-## Step 5: Format Subtask Tree
-
-```
-FOR EACH subtask in currentTask.subtasks:
-  IF index == currentSubtaskIndex:
-    prefix = "🔄"  # Current
-  ELSE IF subtask.status == "completed":
-    prefix = "✅"  # Done
-  ELSE:
-    prefix = "⬜"  # Pending
-
-  connector = (index == last) ? "└─" : "├─"
-  OUTPUT: "   {connector} {prefix} {subtask.description}"
-```
-
----
-
-## Output: Workflow Diagram
-
-```
-📊 WORKFLOW STATUS
-
-┌─────────────────────────────────────────────────────────┐
-│                                                         │
-│   sync ──▶ task ──▶ [work] ──▶ done ──▶ ship           │
-│    ○        ○         ●         ○        ○             │
-│                       ▲                                 │
-│                    YOU ARE HERE                         │
-│                                                         │
-└─────────────────────────────────────────────────────────┘
-```
-
-Position indicators:
-- `○` = not active
-- `●` = current position
-- Arrow indicates flow direction
-
----
-
-## Output: Full Status
-
-```
-📊 WORKFLOW STATUS
-
-┌─────────────────────────────────────────────────────────┐
-│   sync ──▶ task ──▶ work ──▶ done ──▶ ship             │
-│    {s}       {t}      {w}      {d}      {h}            │
-└─────────────────────────────────────────────────────────┘
-
-🎯 Current: {currentTask.parentDescription}
-   Branch: {currentTask.branch}
-   Type: {currentTask.type} | Started: {elapsed}
-   {IF linearId: "Linear: {linearId}"}
-
-   Progress: {progressBar} {completed}/{total} subtasks
-   {subtask tree}
-
-⏸️ Paused: {pausedTasks[0].description or "none"}
-
-📋 Queue: {queueCount} tasks
-{IF queueCount > 0:}
-   • {queue[0].description}
-   • {queue[1].description}
-   {... up to 3}
-
-🚀 Last ship: {previousTask.description} ({daysSince})
-   {IF previousTask.prUrl: "PR: {prUrl}"}
-
-📡 Context: {staleness status}
-   Last sync: {timeSinceSync}
-   {IF isStale: "⚠️ Run `p. sync` to refresh"}
-```
-
----
-
-## Output: Compact (`p. status compact`)
-
-Single-line summary:
-
-```
-{position_emoji} {currentTask.description} │ {progressBar} {completed}/{total} │ 📋 {queueCount} │ {staleness_emoji}
-```
-
-Position emojis:
-- 🔄 = working
-- 👀 = reviewing
-- ✅ = shipped
-- 💤 = idle
-
-Staleness emojis:
-- ✅ = fresh
-- ⚠️ = stale
-
----
-
-## Output: No Active Task
-
-```
-📊 WORKFLOW STATUS
-
-┌─────────────────────────────────────────────────────────┐
-│   sync ──▶ task ──▶ work ──▶ done ──▶ ship             │
-│    ●        ○        ○        ○        ○               │
-└─────────────────────────────────────────────────────────┘
-
-💤 No active task
-
-📋 Queue: {queueCount} tasks
-{IF queueCount > 0:}
-   • {queue[0].description}
-
-🚀 Last ship: {previousTask.description} ({daysSince})
-
-Next: `p. task "description"` or `p. task PRJ-XXX`
-```
-
----
-
-## Elapsed Time Formatting
-
-```
-IF minutes < 60: "{minutes}m"
-ELSE IF hours < 24: "{hours}h {minutes}m"
-ELSE: "{days}d {hours}h"
-```
-
----
-
-## Context Staleness
-
-From `prjct status --json`:
-```json
-{
-  "isStale": true,
-  "commitsSinceSync": 15,
-  "daysSinceSync": 3,
-  "significantChanges": ["package.json", "tsconfig.json"]
-}
-```
-
-Display:
-- Fresh (< 10 commits, < 3 days): `✅ Fresh (synced {time} ago)`
-- Stale: `⚠️ Stale ({commits} commits, {days}d) - run p. sync`