Template

Files

lmiranda 2e65b60725 refactor(projman): extract skills and consolidate commands

Major refactoring of projman plugin architecture:

Skills Extraction (17 new files):
- Extracted reusable knowledge from commands and agents into skills/
- branch-security, dependency-management, git-workflow, input-detection
- issue-conventions, lessons-learned, mcp-tools-reference, planning-workflow
- progress-tracking, repo-validation, review-checklist, runaway-detection
- setup-workflows, sprint-approval, task-sizing, test-standards, wiki-conventions

Command Consolidation (17 → 12 commands):
- /setup: consolidates initial-setup, project-init, project-sync (--full/--quick/--sync)
- /debug: consolidates debug-report, debug-review (report/review modes)
- /test: consolidates test-check, test-gen (run/gen modes)
- /sprint-status: absorbs sprint-diagram via --diagram flag

Architecture Cleanup:
- Remove plugin-level mcp-servers/ symlinks (6 plugins)
- Remove plugin README.md files (12 files, ~2000 lines)
- Update all documentation to reflect new command structure
- Fix documentation drift in CONFIGURATION.md, COMMANDS-CHEATSHEET.md

Commands are now thin dispatchers (~20-50 lines) that reference skills.
Agents reference skills for domain knowledge instead of inline content.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-30 15:02:16 -05:00

2.5 KiB

Raw Blame History

name, description

name	description
input-detection	Detect planning input source (file, wiki, or conversation)

Input Source Detection

Purpose

Defines how to detect where planning input is coming from and how to handle each source.

When to Use

Planner agent: At start of sprint planning
Commands: /sprint-plan

Detection Priority

Priority	Source	Detection	Action
1	Local file	`docs/changes/*.md` exists	Parse frontmatter, migrate to wiki, delete local
2	Existing wiki	`Change VXX.X.X: Proposal` exists	Use as-is, create implementation page
3	Conversation	Neither exists	Create wiki from discussion context

Local File Format

---
version: "4.1.0"        # or "sprint-17" for internal work
title: "Feature Name"
plugin: plugin-name     # optional
type: feature           # feature | bugfix | refactor | infra
---

# Feature Description
[Free-form content...]

Detection Steps

Check for local files:
```
ls docs/changes/*.md
```

Check for existing wiki proposal:

list_wiki_pages(repo="org/repo")
# Filter for "Change V" prefix matching version

If neither found: Use conversation context
If multiple sources found: Ask user which to use

Report to User

Input source detected:
✓ Found: docs/changes/v4.1.0-wiki-planning.md
  - Version: 4.1.0
  - Title: Wiki-Based Planning Workflow
  - Type: feature

I'll use this as the planning input. Proceed? (y/n)

Migration Flow (Local File → Wiki)

When using local file as input:

Parse frontmatter to extract metadata
Create wiki proposal page: Change V4.1.0: Proposal
Create implementation page: Change V4.1.0: Proposal (Implementation 1)
Delete local file - wiki is now source of truth

Migration complete:
✓ Created: "Change V4.1.0: Proposal" (wiki)
✓ Created: "Change V4.1.0: Proposal (Implementation 1)" (wiki)
✓ Deleted: docs/changes/v4.1.0-wiki-planning.md (migrated)

Ambiguous Input Handling

If multiple valid sources found:

Multiple input sources detected:

1. Local file: docs/changes/v4.1.0-feature.md
   - Version: 4.1.0
   - Title: New Feature

2. Wiki proposal: Change V4.1.0: Proposal
   - Status: In Progress
   - Date: 2026-01-20

Which should I use for planning?
  [1] Local file (will migrate to wiki)
  [2] Existing wiki proposal
  [3] Start fresh from conversation

2.5 KiB Raw Blame History