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>

plugins/projman/skills/planning-workflow.md

@@ -0,0 +1,134 @@
+---
+name: planning-workflow
+description: The complete sprint planning process steps
+---
+
+# Planning Workflow
+
+## Purpose
+
+Defines the complete 11-step planning workflow from validation through approval.
+
+## When to Use
+
+- **Planner agent**: When executing `/sprint-plan`
+- **Commands**: `/sprint-plan`
+
+---
+
+## Workflow Steps
+
+### 1. Understand Sprint Goals
+
+Ask clarifying questions:
+- What are the sprint objectives?
+- What's the scope and priority?
+- Are there any constraints (time, resources, dependencies)?
+- What's the desired outcome?
+
+**Never rush - take time to understand requirements fully.**
+
+### 2. Run Pre-Planning Validations
+
+Execute in order:
+1. **Branch detection** - See `skills/branch-security.md`
+2. **Repository org check** - See `skills/repo-validation.md`
+3. **Label taxonomy validation** - See `skills/repo-validation.md`
+
+**STOP if any validation fails.**
+
+### 3. Detect Input Source
+
+Follow `skills/input-detection.md`:
+1. Check for `docs/changes/*.md` files
+2. Check for existing wiki proposal
+3. If neither: use conversation context
+4. If ambiguous: ask user
+
+### 4. Search Relevant Lessons Learned
+
+Follow `skills/lessons-learned.md`:
+```python
+search_lessons(repo="org/repo", query="sprint keywords", tags=["relevant", "tags"])
+```
+
+Present findings to user before proceeding.
+
+### 5. Create/Update Wiki Proposal
+
+Follow `skills/wiki-conventions.md`:
+- If local file: migrate content to wiki, create proposal page
+- If conversation: create proposal from discussion
+- If existing wiki: skip creation, use as-is
+
+### 6. Create Wiki Implementation Page
+
+Follow `skills/wiki-conventions.md`:
+- Create `Change VXX.X.X: Proposal (Implementation N)`
+- Update proposal page with link to implementation
+
+### 7. Architecture Analysis
+
+Think through:
+- What components will be affected?
+- What are the integration points?
+- Are there edge cases to handle?
+- What dependencies exist?
+- What are potential risks?
+
+### 8. Create Gitea Issues
+
+Follow `skills/issue-conventions.md` and `skills/task-sizing.md`:
+- Use proper title format: `[Sprint XX] <type>: <description>`
+- Include wiki implementation reference
+- Apply appropriate labels using `suggest_labels`
+- **Refuse to create L/XL tasks without breakdown**
+
+### 9. Set Up Dependencies
+
+```python
+create_issue_dependency(repo="org/repo", issue_number=46, depends_on=45)
+```
+
+### 10. Create or Select Milestone
+
+```python
+create_milestone(
+    repo="org/repo",
+    title="Sprint 17 - Feature Name",
+    description="Sprint description",
+    due_on="2025-02-01T00:00:00Z"
+)
+```
+
+Assign issues to the milestone.
+
+### 11. Request Sprint Approval
+
+Follow `skills/sprint-approval.md`:
+- Present approval request with scope summary
+- Wait for explicit user approval
+- Record approval in milestone description
+
+---
+
+## Cleanup After Planning
+
+- Delete local input file (wiki is now source of truth)
+- Summarize architectural decisions
+- List created issues with labels
+- Document dependency graph
+- Provide sprint overview with wiki links
+
+---
+
+## Visual Output
+
+Display header at start:
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🎯 PLANNING                                                     ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```