agileflow 2.76.0 → 2.78.0

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

@@ -1,6 +1,20 @@
 ---
 description: Edit an existing skill's SKILL.md, cookbook entries, or references
 argument-hint: [SKILL_NAME] (optional)
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:skill:edit - Modifies existing skills"
+    - "MUST list available skills if SKILL_NAME not provided"
+    - "MUST show skill structure before asking what to edit"
+    - "MUST offer special edits: rename, add cookbook, full rewrite (Plan Mode)"
+    - "MUST preview changes with diff before writing"
+    - "MUST ask for confirmation before any file writes"
+    - "For full rewrite: MUST enter Plan Mode and research before regenerating"
+  state_fields:
+    - selected_skill
+    - edit_target_file
+    - has_changes_pending
 ---
 
 # /agileflow:skill:edit
@@ -9,6 +23,96 @@ Modify an existing skill in `.claude/skills/`.
 
 ---
 
+<!-- COMPACT_SUMMARY_START -->
+
+## 🚨 COMPACT SUMMARY - /agileflow:skill:edit IS ACTIVE
+
+**CRITICAL**: This command modifies existing skills with preview and confirmation.
+
+### 🚨 RULE #1: Select Skill
+If SKILL_NAME not provided:
+```bash
+ls -d .claude/skills/*/ | xargs -I {} basename {}
+```
+Show options and ask user which to edit.
+
+### 🚨 RULE #2: Show Skill Structure
+Display current skill contents before asking what to edit:
+```
+📝 Editing: skill-name
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Files:
+  1. SKILL.md (main skill file)
+  2. references.md (documentation links)
+  3. cookbook/use-case-1.md
+  4. cookbook/use-case-2.md
+  5. .mcp.json (MCP configuration)
+```
+
+### 🚨 RULE #3: Ask What to Edit
+Offer these options:
+1. **SKILL.md** - Main skill instructions
+2. **references.md** - Update documentation links
+3. **Cookbook entry** - Edit specific use-case workflow
+4. **Add new cookbook** - Create new use-case workflow
+5. **MCP configuration** - Modify MCP server settings
+6. **Rename skill** - Change skill name and folder
+
+### 🚨 RULE #4: Read Current Content
+Before editing, always read the file:
+```bash
+cat .claude/skills/<skill>/<file>
+```
+
+### 🚨 RULE #5: Preview Before Writing
+For any change:
+1. Show diff preview (- old, + new)
+2. Ask for confirmation
+3. Only write if confirmed
+
+### 🚨 RULE #6: Special Edits
+| Edit Type | Process |
+|-----------|---------|
+| Full rewrite | Enter Plan Mode, research, generate with approval |
+| Rename | Validate name, create new dir, copy files, update frontmatter, delete old |
+| Add cookbook | Create from template, update SKILL.md references |
+| Regular edits | Read → Edit → Preview → Confirm → Write |
+
+### 🚨 RULE #7: For Full Rewrite
+If user selects "Full rewrite (Recommended)":
+1. Enter Plan Mode
+2. Research web/local/codebase again
+3. Show updated plan to user
+4. Get approval
+5. Exit Plan Mode
+6. Regenerate the file with new research
+
+### Critical Edit Operations
+| Operation | Check | Action |
+|-----------|-------|--------|
+| Rename | Name is valid | Copy dir + update frontmatter + delete old |
+| Add cookbook | Template ready | Create file + update SKILL.md |
+| Change SKILL.md | Diff ready | Show preview + confirm + write |
+| Modify references.md | Links valid | Show preview + confirm + write |
+
+### Anti-Patterns
+- ❌ DON'T modify files without preview
+- ❌ DON'T skip diff confirmation
+- ❌ DON'T rename without validating new name
+- ❌ DON'T offer "full rewrite" without Plan Mode
+- ❌ DON'T leave skill in broken state (always backup before changes)
+
+### REMEMBER AFTER COMPACTION
+- Edit is always: Select → Show structure → Ask what → Read → Edit → Preview → Confirm → Write
+- Full rewrite means Plan Mode + research + approval
+- Always show diffs before writing
+- Rename requires copying and updating frontmatter
+- New cookbook entries need SKILL.md updated too
+
+<!-- COMPACT_SUMMARY_END -->
+
+---
+
 ## Workflow
 
 ### STEP 1: Select skill to edit

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

@@ -1,6 +1,18 @@
 ---
 description: List all installed skills with their descriptions and status
 argument-hint: (no arguments)
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:skill:list - Shows installed skills inventory"
+    - "MUST scan .claude/skills/ directory for all skill subdirectories"
+    - "MUST extract name/description from each SKILL.md frontmatter"
+    - "MUST count supporting files (cookbook/*, references.md, .mcp.json)"
+    - "MUST show MCP status indicator if .mcp.json exists"
+    - "MUST offer skill management actions after listing"
+  state_fields:
+    - skills_found_count
+    - has_mcp_skills
 ---
 
 # /agileflow:skill:list
@@ -9,6 +21,79 @@ Display all skills installed in `.claude/skills/` with their metadata.
 
 ---
 
+<!-- COMPACT_SUMMARY_START -->
+
+## 🚨 COMPACT SUMMARY - /agileflow:skill:list IS ACTIVE
+
+**CRITICAL**: This command inventories all installed skills and their metadata.
+
+### 🚨 RULE #1: Check Directory Exists
+```bash
+ls -la .claude/skills/ 2>/dev/null
+```
+If directory missing or empty, show helpful message to create a skill.
+
+### 🚨 RULE #2: Scan Each Skill
+For EACH subdirectory in `.claude/skills/`:
+1. Read SKILL.md frontmatter for `name:` and `description:`
+2. Count supporting files:
+   - cookbook/*.md (all files)
+   - references.md (if exists)
+   - .mcp.json (if exists)
+3. Check for MCP: If `.mcp.json` exists, mark "MCP: ✓"
+
+### 🚨 RULE #3: Format Output
+Display in clean table format:
+```
+📦 Installed Skills (N total)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+skill-name              Description here     MCP: ✓
+  └─ X files: file1, file2, file3
+```
+
+### 🚨 RULE #4: Show File Count
+- Total files per skill (SKILL.md + references.md + cookbook/*.md + .mcp.json)
+- List cookbook files by name (only cookbook/, not full path)
+- Note MCP configuration status
+
+### 🚨 RULE #5: Offer Actions After Listing
+After showing all skills, ask:
+```
+What would you like to do?
+- Create new skill
+- Edit a skill
+- Delete a skill
+- Test a skill
+- Done
+```
+
+### Critical Output Elements
+| Element | Shows |
+|---------|-------|
+| Total count | "N total" in header |
+| Skill names | From SKILL.md `name:` field |
+| Description | From SKILL.md `description:` field |
+| File count | Total files in skill directory |
+| MCP status | "✓" if .mcp.json exists, nothing otherwise |
+
+### Anti-Patterns
+- ❌ DON'T fail if directory doesn't exist (create helpful message)
+- ❌ DON'T list hidden files or system files
+- ❌ DON'T show full file paths (just filenames)
+- ❌ DON'T try to parse corrupt SKILL.md (skip with warning)
+- ❌ DON'T forget to offer next actions
+
+### REMEMBER AFTER COMPACTION
+- List is inventory-only, no modifications
+- Always scan .claude/skills/ directory
+- Extract metadata from SKILL.md frontmatter
+- Show file counts and MCP status indicators
+- Offer management actions after listing
+
+<!-- COMPACT_SUMMARY_END -->
+
+---
+
 ## Output Format
 
 ```
@@ -153,3 +238,46 @@ If frontmatter can't be parsed:
 # List all installed skills
 /agileflow:skill:list
 ```
+
+---
+
+## POST-LISTING ACTIONS
+
+After displaying the skill inventory, offer actions:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "What would you like to do?",
+  "header": "Actions",
+  "multiSelect": false,
+  "options": [
+    {"label": "Create new skill", "description": "Build a research-backed custom skill"},
+    {"label": "Test a skill", "description": "Verify a skill works correctly"},
+    {"label": "Edit a skill", "description": "Modify an existing skill"},
+    {"label": "Done", "description": "Exit"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+**If "Create new skill"**:
+- Run `/agileflow:skill:create`
+
+**If "Test a skill"**:
+- Ask which skill to test
+- Run `/agileflow:skill:test SKILL=<selected>`
+
+**If "Edit a skill"**:
+- Ask which skill to edit
+- Run `/agileflow:skill:edit SKILL=<selected>`
+
+---
+
+## Related Commands
+
+- `/agileflow:skill:create` - Build new research-backed skill
+- `/agileflow:skill:test` - Test a skill with sample inputs
+- `/agileflow:skill:edit` - Modify an existing skill
+- `/agileflow:skill:delete` - Remove a skill
+- `/agileflow:skill:upgrade` - Update skill with new patterns

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

@@ -1,6 +1,20 @@
 ---
 description: Verify a skill works correctly by testing its activation and functionality
 argument-hint: [SKILL_NAME] (optional)
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:skill:test - Validates skill structure and functionality"
+    - "MUST list available skills if SKILL_NAME not provided"
+    - "MUST run structure validation checks (file existence, frontmatter, sizes)"
+    - "MUST run content validation checks (section presence, file references)"
+    - "MUST offer optional activation test with sample prompts"
+    - "MUST generate test report with pass/fail/warning indicators"
+    - "MUST suggest fixes for validation failures"
+  state_fields:
+    - selected_skill
+    - validation_results
+    - test_report_generated
 ---
 
 # /agileflow:skill:test
@@ -9,6 +23,127 @@ Test a skill to verify it activates correctly and produces expected results.
 
 ---
 
+<!-- COMPACT_SUMMARY_START -->
+
+## 🚨 COMPACT SUMMARY - /agileflow:skill:test IS ACTIVE
+
+**CRITICAL**: This command validates skills through structure, content, and optional activation testing.
+
+### 🚨 RULE #1: Select Skill
+If SKILL_NAME not provided:
+```bash
+ls -d .claude/skills/*/ | xargs -I {} basename {}
+```
+Show options and ask user which to test.
+
+### 🚨 RULE #2: Run Structure Validation
+Check these in order:
+```
+✅ SKILL.md exists (file present)
+✅ Frontmatter has name and description
+✅ references.md exists
+⚠️  cookbook/ directory (ok if missing for simple skills)
+⚠️  .mcp.json (ok if MCP not configured)
+```
+
+### 🚨 RULE #3: Run Content Validation
+Check these in order:
+```
+✅ "When to Use" section present
+✅ Description under 1024 characters
+✅ SKILL.md under 500 lines
+✅ All cookbook files referenced in SKILL.md actually exist
+```
+
+### 🚨 RULE #4: Show Validation Results
+Display in report format:
+```
+🧪 Testing: skill-name
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Structure:     ✅ PASS (5/5 checks)
+Content:       ✅ PASS (4/4 checks)
+MCP Config:    ⚠️  NOT CONFIGURED
+
+Overall: ✅ SKILL IS FUNCTIONAL
+```
+
+### 🚨 RULE #5: Offer Activation Test (Optional)
+Ask after structure/content validation:
+```
+Would you like to test skill activation with sample prompts?
+- Yes, test activation (Recommended)
+- Skip activation test
+- View SKILL.md content
+```
+
+### 🚨 RULE #6: Run Activation Test (if requested)
+1. Extract sample triggers from "When to Use" section
+2. Present 2-3 test prompts to user
+3. Ask user to pick one or provide custom
+4. Execute skill by reading SKILL.md and following instructions
+5. Report activation results
+
+### 🚨 RULE #7: Generate Final Report
+Report MUST include:
+- Structure validation pass/fail
+- Content validation pass/fail
+- Activation test pass/fail (if run)
+- Issues found (if any)
+- Recommendations (if any)
+- Overall status: PASS/WARNINGS/FAIL
+
+### Validation Checks Table
+| Category | Check | Pass Condition |
+|----------|-------|----------------|
+| Structure | SKILL.md exists | File present |
+| Structure | Frontmatter valid | Has name + description |
+| Structure | references.md | File exists (optional) |
+| Structure | cookbook/ | Directory exists (optional) |
+| Content | When to Use | Section present with triggers |
+| Content | Description | Under 1024 characters |
+| Content | SKILL.md size | Under 500 lines |
+| Content | Cookbook refs | All files exist |
+| MCP | JSON valid | Parses without errors |
+| MCP | mcpServers | Object present |
+
+### Test Report Format
+```
+🧪 Skill Test Report: <skill-name>
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+STRUCTURE VALIDATION
+  ✅ SKILL.md exists
+  ✅ Frontmatter valid
+  ⚠️  references.md exists
+  ✅ cookbook/ directory
+
+CONTENT VALIDATION
+  ✅ "When to Use" section
+  ✅ Description < 1024 chars (456)
+  ✅ SKILL.md < 500 lines (287)
+  ✅ Cookbook refs valid
+
+OVERALL: ✅ PASS
+```
+
+### Anti-Patterns
+- ❌ DON'T skip structure validation (foundation of quality)
+- ❌ DON'T fail on missing optional files (warn instead)
+- ❌ DON'T run activation test without user consent
+- ❌ DON'T generate complex test prompts (keep simple)
+- ❌ DON'T forget to suggest fixes for failures
+
+### REMEMBER AFTER COMPACTION
+- Test has 2-3 phases: Structure → Content → [Activation if requested]
+- Always generate full report with pass/fail indicators
+- Activation test is optional (ask first)
+- Warn on optional files missing, fail on required files
+- Suggest fixes for any validation failures
+
+<!-- COMPACT_SUMMARY_END -->
+
+---
+
 ## Workflow
 
 ### STEP 1: Select skill to test