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.3 KiB

Raw Blame History

description

description
Configure projman - full setup, quick project init, or sync after repo move

Setup

Skills Required

skills/mcp-tools-reference.md
skills/repo-validation.md
skills/setup-workflows.md

Purpose

Unified setup command for all configuration needs.

Important:

Uses Bash, Read, Write, AskUserQuestion - NOT MCP tools
MCP tools won't work until after setup + session restart
Tokens must be entered manually for security

Invocation

/setup              # Auto-detect appropriate mode
/setup --full       # Full wizard (MCP + system + project)
/setup --quick      # Project-only setup
/setup --sync       # Update after repo move

Mode Detection

If no argument provided, auto-detect:

Check ~/.config/claude/gitea.env
- Missing → full mode
Check project .env
- Missing → quick mode
Compare .env with git remote
- Mismatch → sync mode
- Match → offer reconfigure or exit

Mode: Full

Execute skills/setup-workflows.md → Full Setup Workflow

Phases:

Environment validation (Python 3.10+)
MCP server setup (venv + requirements)
System-level config (~/.config/claude/gitea.env)
Project-level config (.env)
Final validation

Mode: Quick

Execute skills/setup-workflows.md → Quick Setup Workflow

Steps:

Verify system config exists
Verify git repository
Check existing .env
Detect org/repo from git remote
Validate via API
Create/update .env
Check .gitignore

Mode: Sync

Execute skills/setup-workflows.md → Sync Workflow