agileflow 3.4.3 → 4.0.0-alpha.2

package/src/core/commands/session/status.md

@@ -1,274 +0,0 @@
----
-description: View current session state and activity
-argument-hint: "[--kanban]"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:session:status - Display all sessions in table"
-    - "Does NOT prompt for action (read-only display)"
-    - "Shows current session, then table of other sessions"
-    - "Marks active sessions with ● bullet, inactive with ○"
-    - "Returns session count and active count"
-    - "--kanban flag shows Kanban-style board with phases (TO DO, CODING, REVIEW, MERGED)"
-  state_fields:
-    - current_session
-    - all_sessions
-    - active_count
-    - total_count
----
-
-# /agileflow:session:status
-
-Quick view of all sessions and their status.
-
----
-
-## Purpose
-
-Display a compact overview of all registered sessions without prompting for action.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js session:status
-```
-
----
-
-## Arguments
-
-| Argument | Required | Description |
-|----------|----------|-------------|
-| `--kanban` | No | Show Kanban-style board with phases instead of table |
-
-## IMMEDIATE ACTIONS
-
-### Step 1: Get Session Data
-
-**Standard view:**
-```bash
-node .agileflow/scripts/session-manager.js list --json
-```
-
-**Kanban view (if --kanban flag):**
-```bash
-node .agileflow/scripts/session-manager.js list --kanban
-```
-
-### Step 2: Display Formatted Output
-
-**Standard Table View:**
-```
-📊 Session Status
-
-Current: Session 1 (main)
-         Branch: main │ Story: US-0042 │ Active
-
-Other Sessions:
-┌─────┬──────────────────┬─────────────┬────────────┐
-│  #  │ Name/Branch      │ Story       │ Status     │
-├─────┼──────────────────┼─────────────┼────────────┤
-│  2  │ "auth"           │ US-0038     │ ● Active   │
-│  3  │ feature/payments │ -           │ ○ Inactive │
-└─────┴──────────────────┴─────────────┴────────────┘
-
-Total: 3 sessions │ 2 active
-```
-
-**Kanban Board View (--kanban):**
-```
-Sessions (Kanban View):
-
-TO DO           CODING          REVIEW          MERGED
-┌──────────────┐  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐
-│              │  │[2] auth      │  │[3] payments  │  │[1] main      │
-│              │  │US-0038       │  │US-0042       │  │-             │
-└──────────────┘  └──────────────┘  └──────────────┘  └──────────────┘
-
-To Do: 0 │ Coding: 1 │ Review: 1 │ Merged: 1
-```
-
-**Phase Detection Logic:**
-- **TO DO**: No commits since branch creation
-- **CODING**: Has commits, still has uncommitted changes
-- **REVIEW**: Has commits, no uncommitted changes (ready to merge)
-- **MERGED**: Main branch or merged sessions
-
-### Step 3: Show Quick Actions
-
-```
-💡 Quick actions:
-   /agileflow:session:new    - Create parallel session
-   /agileflow:session:resume - Switch to another session
-   /agileflow:session:end    - End current session
-```
-
-## No Sessions Case
-
-```
-📊 Session Status
-
-No sessions registered yet. You're in the main project directory.
-Run /agileflow:session:new to create a parallel workspace.
-```
-
-## Related Commands
-
-- `/agileflow:session:new` - Create new session
-- `/agileflow:session:resume` - Switch sessions
-- `/agileflow:session:end` - End current session
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## ⚠️ COMPACT SUMMARY - /agileflow:session:status IS ACTIVE
-
-**CRITICAL**: This command displays read-only status. It NEVER prompts for action - just shows information.
-
----
-
-### 🚨 RULE #1: READ-ONLY DISPLAY (NO USER PROMPTS)
-
-**NEVER use AskUserQuestion or present options.** This command is informational only.
-
-| Command | Has Prompts? | Use Case |
-|---------|-------------|----------|
-| `/agileflow:session:status` | ❌ No | Quick info view |
-| `/agileflow:session:resume` | ✅ Yes | Switch sessions |
-| `/agileflow:session:new` | ✅ Yes | Create session |
-| `/agileflow:session:end` | ✅ Yes | End session |
-
----
-
-### 🚨 RULE #2: DISPLAY FORMAT
-
-**Structure:**
-1. Header with emoji: `📊 Session Status`
-2. Current session info (highlighted)
-3. Table of other sessions
-4. Summary line: `Total: X sessions │ Y active`
-5. Quick actions (optional)
-
-**Example:**
-```
-📊 Session Status
-
-Current: Session 1 (main)
-         Branch: main │ Story: US-0042 │ Active
-
-Other Sessions:
-┌─────┬──────────────────┬─────────────┬────────────┐
-│  #  │ Name/Branch      │ Story       │ Status     │
-├─────┼──────────────────┼─────────────┼────────────┤
-│  2  │ "auth"           │ US-0038     │ ● Active   │
-│  3  │ feature/payments │ -           │ ○ Inactive │
-└─────┴──────────────────┴─────────────┴────────────┘
-
-Total: 3 sessions │ 2 active
-```
-
----
-
-### 🚨 RULE #3: STATUS BULLETS
-
-- **● Active** - Session has lock file (Claude process running)
-- **○ Inactive** - No lock file (can be resumed)
-
----
-
-### 🚨 RULE #4: SHOW QUICK ACTIONS (OPTIONAL)
-
-After the table, show optional quick actions info:
-```
-💡 Quick actions:
-   /agileflow:session:new    - Create parallel session
-   /agileflow:session:resume - Switch to another session
-   /agileflow:session:end    - End current session
-```
-
----
-
-### 🚨 RULE #5: HANDLE EDGE CASES
-
-**If no sessions exist:**
-```
-📊 Session Status
-
-No sessions registered yet. You're in the main project directory.
-Run /agileflow:session:new to create a parallel workspace.
-```
-
-**If only current session:**
-```
-📊 Session Status
-
-Current: Session 1 (main)
-         Branch: main │ Active
-
-This is your only session. Use /agileflow:session:new to create more.
-```
-
----
-
-### FORMATTING RULES
-
-| Element | Format | Example |
-|---------|--------|---------|
-| Session name | Branch or nickname | `main` or `"auth"` |
-| Story ID | US-#### or dash | `US-0042` or `-` |
-| Status | ● Active or ○ Inactive | `● Active` |
-| Session reference | Session {id} | `Session 1` |
-
----
-
-### KEY FILES TO REMEMBER
-
-| File | Purpose |
-|------|---------|
-| `.agileflow/sessions/registry.json` | Master list of sessions |
-| `.agileflow/sessions/{id}.lock` | Lock file marks session active |
-| `.agileflow/scripts/session-manager.js` | Data source |
-
----
-
-### WORKFLOW
-
-1. **Get sessions** → `node .agileflow/scripts/session-manager.js list --json`
-2. **Parse JSON** → Extract sessions, identify current
-3. **Build display** → Format header, current session, table
-4. **Show summary** → Total and active counts
-5. **Optionally show** → Quick actions reference
-
----
-
-### ANTI-PATTERNS (DON'T DO THESE)
-
-❌ Use AskUserQuestion to prompt for action
-❌ Show "Resume Session 2?" or similar prompts
-❌ Use table without proper formatting
-❌ Show path in table (too much info)
-❌ Skip summary line showing counts
-
-### DO THESE INSTEAD
-
-✅ Display as read-only information
-✅ Use ● and ○ bullets for status
-✅ Format table with proper borders
-✅ Show summary with counts
-✅ Optionally show quick actions for reference
-
----
-
-### REMEMBER AFTER COMPACTION
-
-- `/agileflow:session:status` IS ACTIVE
-- NEVER prompt for action (read-only display)
-- Format: header + current session + table + summary
-- Use ● for active, ○ for inactive
-- Show session counts in summary
-- Optionally show quick actions reference
-
-<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/skill/list.md

@@ -1,139 +0,0 @@
----
-description: List installed skills and browse recommended skills from the marketplace
-argument-hint: "(no arguments)"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:skill:list - Shows installed + recommended skills"
-    - "MUST scan .claude/skills/ directory for installed skill subdirectories"
-    - "MUST extract name/description from each SKILL.md frontmatter"
-    - "MUST show recommended skills based on detected tech stack"
-    - "MUST provide install commands for marketplace skills"
-    - "MUST offer actions: recommend more, browse marketplace, done"
-  state_fields:
-    - skills_found_count
-    - recommendations_shown
----
-
-# /agileflow:skill:list
-
-Display installed skills and recommended skills from the skills.sh marketplace.
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## COMPACT SUMMARY - /agileflow:skill:list IS ACTIVE
-
-**CRITICAL**: This command shows installed skills AND marketplace recommendations.
-
-### RULE #1: Show Installed Skills
-Scan `.claude/skills/` for subdirectories with SKILL.md. For each:
-- Extract name/description from frontmatter
-- Count files (cookbook/*, references.md)
-- Display in clean format
-
-### RULE #2: Show Recommended Skills
-Based on the project's tech stack (from package.json and project files):
-- Detect frameworks, databases, testing, styling
-- Match against curated skills catalog
-- Show top matches with install commands
-
-### RULE #3: Provide Install Commands
-Each recommended skill shows: `npx skills add owner/repo`
-
-### RULE #4: Offer Actions
-After listing, offer: Get more recommendations, Browse marketplace, Done
-
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## Workflow
-
-### STEP 1: Show installed skills
-
-Scan `.claude/skills/` for subdirectories:
-
-```bash
-ls -la .claude/skills/ 2>/dev/null
-```
-
-For each subdirectory with SKILL.md:
-1. Read frontmatter for `name:` and `description:`
-2. Count supporting files (cookbook/*, references.md)
-
-Display format:
-```
-Installed Skills (N total)
-
-  skill-name - Description here
-    Files: SKILL.md, references.md, cookbook/use-case.md
-
-  another-skill - Another description
-    Files: SKILL.md, cookbook/workflow.md
-```
-
-If no skills installed:
-```
-No skills installed yet.
-Install from the marketplace with: npx skills add owner/repo
-Or browse recommendations: /agileflow:skill:recommend
-```
-
-### STEP 2: Detect tech stack
-
-Read `package.json` dependencies and scan project files to detect:
-- **Frameworks**: React, Next.js, Vue, Svelte, Express, FastAPI, etc.
-- **Databases**: Prisma, Supabase, MongoDB, PostgreSQL, Redis, etc.
-- **Testing**: Jest, Vitest, Playwright, Cypress, pytest, etc.
-- **Styling**: Tailwind, styled-components, Sass, etc.
-- **Languages**: TypeScript, Python, Go, PHP, etc.
-
-### STEP 3: Show top recommendations
-
-Based on detected stack, show top 3-5 matching skills:
-
-```
-Recommended for Your Stack
-
-  Detected: React, Next.js, TypeScript, Tailwind, Prisma, Jest
-
-  Frontend:
-    next-best-practices (95% match) - Next.js App Router, RSC, and data fetching
-      Install: npx skills add vercel/next-skills
-
-    react-best-practices (90% match) - React patterns, hooks, and components
-      Install: npx skills add vercel/agent-skills
-
-  Database:
-    prisma-orm (85% match) - Prisma schema design and query patterns
-      Install: npx skills add mcpmarket/skills
-
-  Testing:
-    jest-testing (80% match) - Jest unit and integration testing patterns
-      Install: npx skills add anthropics/skills
-```
-
-### STEP 4: Offer actions
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "What would you like to do?",
-  "header": "Skills",
-  "multiSelect": false,
-  "options": [
-    {"label": "Get more recommendations", "description": "Run /agileflow:skill:recommend for full results"},
-    {"label": "Browse marketplace", "description": "Run npx skills find to browse all skills"},
-    {"label": "Done", "description": "Exit skill listing"}
-  ]
-}]</parameter>
-</invoke>
-```
-
----
-
-## Related Commands
-
-- `/agileflow:skill:recommend` - Full recommendation engine with detailed matching

package/src/core/commands/skill/recommend.md

@@ -1,216 +0,0 @@
----
-description: Get skill recommendations based on your project's tech stack
-argument-hint: "[keyword]"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:skill:recommend - Tech stack skill recommendations"
-    - "MUST detect tech stack from package.json, project files"
-    - "MUST match against curated skill catalog (~60 vetted skills)"
-    - "MUST show ranked recommendations with install commands"
-    - "MUST filter out already-installed skills"
-    - "MUST offer live search via npx skills search for broader results"
-  state_fields:
-    - detected_stack
-    - recommendations_count
----
-
-# /agileflow:skill:recommend
-
-Get personalized skill recommendations based on your project's detected tech stack. Matches against a curated catalog of ~60 vetted skills from skills.sh, with optional live marketplace search.
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## COMPACT SUMMARY - /agileflow:skill:recommend IS ACTIVE
-
-**CRITICAL**: Detect tech stack, recommend matching skills from curated catalog.
-
-### RULE #1: Detect Tech Stack
-Read package.json deps + scan for project files (Dockerfile, go.mod, etc.)
-Detect: frameworks, databases, testing, styling, languages, devops
-
-### RULE #2: Match Against Catalog
-Score each curated skill by tag overlap with detected stack.
-Show top matches per category with relevance percentage.
-
-### RULE #3: Filter Installed
-Scan .claude/skills/ and exclude already-installed skills.
-
-### RULE #4: Show Install Commands
-Each result: `npx skills add owner/repo`
-
-### RULE #5: Offer Live Search
-For broader results: `npx skills search <keyword>`
-
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## Workflow
-
-### STEP 1: Detect tech stack
-
-Read `package.json` to identify dependencies:
-
-```bash
-cat package.json 2>/dev/null | head -100
-```
-
-Also check for:
-- `requirements.txt`, `pyproject.toml` (Python)
-- `go.mod` (Go)
-- `composer.json` (PHP)
-- `Dockerfile` (Docker)
-- `.github/workflows/` (GitHub Actions)
-- `vercel.json` (Vercel)
-- `terraform/`, `main.tf` (Terraform)
-- `k8s/`, `kubernetes/` (Kubernetes)
-
-Map dependencies to technology tags:
-
-| Dependency | Tags |
-|-----------|------|
-| `next` | next, nextjs, react, app-router |
-| `react` | react, jsx, hooks |
-| `vue` | vue, vuejs, vue3 |
-| `@angular/core` | angular, rxjs |
-| `express` | express, expressjs, node |
-| `tailwindcss` | tailwind, tailwindcss, css |
-| `prisma` | prisma, orm, database |
-| `@supabase/supabase-js` | supabase, postgres, auth |
-| `jest` | jest, testing, javascript |
-| `vitest` | vitest, vite, testing |
-| `playwright` | playwright, e2e, testing |
-| `typescript` | typescript, ts |
-
-### STEP 2: Check installed skills
-
-```bash
-ls .claude/skills/ 2>/dev/null
-```
-
-Collect names of installed skills to filter from recommendations.
-
-### STEP 3: Match and rank skills
-
-The curated catalog contains ~60 skills across 6 categories:
-- **Frontend** (13): React, Next.js, Vue, Svelte, Angular, Tailwind, TypeScript
-- **Backend** (11): GraphQL, Express, FastAPI, Node.js, Go, microservices
-- **Database** (8): Prisma, Supabase, MongoDB, PostgreSQL, Redis, Drizzle
-- **Testing** (10): TDD, Jest, Playwright, Cypress, pytest, Vitest
-- **DevOps** (9): GitHub Actions, Docker, Kubernetes, Terraform, Vercel
-- **Security** (8): OWASP, code review, auth, input validation
-
-Score each skill: count how many of the skill's tags match the detected stack.
-Sort by score descending within each category.
-
-### STEP 4: Display recommendations
-
-Show detected stack first, then recommendations by category:
-
-```
-Detected Tech Stack
-  Frameworks: react, next, typescript
-  Databases: prisma, postgresql
-  Testing: jest, playwright
-  Styling: tailwind
-  DevOps: github-actions, docker
-
-Recommended Skills (12 matches)
-
-Frontend
-  next-best-practices (95% match) - Next.js App Router, RSC, and data fetching
-    Install: npx skills add vercel/next-skills
-
-  react-best-practices (90% match) - React patterns, hooks, and component architecture
-    Install: npx skills add vercel/agent-skills
-
-  tailwind-mastery (85% match) - Tailwind CSS utility patterns and custom configurations
-    Install: npx skills add anthropics/skills
-
-Database
-  prisma-orm (90% match) - Prisma schema design, migrations, and query patterns
-    Install: npx skills add mcpmarket/skills
-
-  postgresql-advanced (75% match) - PostgreSQL advanced queries and performance
-    Install: npx skills add anthropics/skills
-
-Testing
-  jest-testing (85% match) - Jest unit and integration testing patterns
-    Install: npx skills add anthropics/skills
-
-  playwright-automation (80% match) - Playwright e2e testing and browser automation
-    Install: npx skills add anthropics/skills
-
-DevOps
-  github-actions (75% match) - GitHub Actions workflow design and optimization
-    Install: npx skills add anthropics/skills
-
-  dockerfile-best-practices (70% match) - Dockerfile optimization and security
-    Install: npx skills add anthropics/skills
-```
-
-### STEP 5: Offer actions
-
-If the user provided a keyword argument, also search the curated catalog by keyword.
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "What would you like to do?",
-  "header": "Install",
-  "multiSelect": false,
-  "options": [
-    {"label": "Install a skill", "description": "Copy the install command for a recommended skill"},
-    {"label": "Search marketplace", "description": "Run npx skills search <keyword> for broader results"},
-    {"label": "Browse all skills", "description": "Run npx skills find to see the full marketplace"},
-    {"label": "Done", "description": "Exit recommendations"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**If "Install a skill"**: Ask which skill, then provide the exact `npx skills add` command.
-
-**If "Search marketplace"**: Ask for a keyword, then run `npx skills search <keyword>`.
-
-**If "Browse all skills"**: Run `npx skills find`.
-
----
-
-## Optional Keyword Argument
-
-If called with a keyword:
-```bash
-/agileflow:skill:recommend react
-```
-
-Filter recommendations to skills matching that keyword in name, description, or tags.
-
----
-
-## Error Handling
-
-### No package.json
-```
-Could not detect tech stack (no package.json found).
-You can still browse the marketplace:
-  npx skills find
-  npx skills search <keyword>
-```
-
-### No Matches
-```
-No curated skills match your tech stack.
-Try searching the marketplace:
-  npx skills search <your-technology>
-  npx skills find
-```
-
----
-
-## Related Commands
-
-- `/agileflow:skill:list` - View installed skills with marketplace preview