lmiranda
2e65b60725
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>
91 lines
2.3 KiB
Markdown
91 lines
2.3 KiB
Markdown
---
|
|
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:
|
|
|
|
1. Check `~/.config/claude/gitea.env`
|
|
- Missing → **full** mode
|
|
|
|
2. Check project `.env`
|
|
- Missing → **quick** mode
|
|
|
|
3. Compare `.env` with git remote
|
|
- Mismatch → **sync** mode
|
|
- Match → offer reconfigure or exit
|
|
|
|
## Mode: Full
|
|
|
|
Execute `skills/setup-workflows.md` → Full Setup Workflow
|
|
|
|
Phases:
|
|
1. Environment validation (Python 3.10+)
|
|
2. MCP server setup (venv + requirements)
|
|
3. System-level config (`~/.config/claude/gitea.env`)
|
|
4. Project-level config (`.env`)
|
|
5. Final validation
|
|
|
|
## Mode: Quick
|
|
|
|
Execute `skills/setup-workflows.md` → Quick Setup Workflow
|
|
|
|
Steps:
|
|
1. Verify system config exists
|
|
2. Verify git repository
|
|
3. Check existing `.env`
|
|
4. Detect org/repo from git remote
|
|
5. Validate via API
|
|
6. Create/update `.env`
|
|
7. Check `.gitignore`
|
|
|
|
## Mode: Sync
|
|
|
|
Execute `skills/setup-workflows.md` → Sync Workflow
|
|
|
|
Steps:
|
|
1. Read current config
|
|
2. Detect git remote
|
|
3. Compare values
|
|
4. Show changes
|
|
5. Validate new values
|
|
6. Update `.env`
|
|
7. Confirm
|
|
|
|
## Visual Output
|
|
|
|
```
|
|
╔══════════════════════════════════════════════════════════════════╗
|
|
║ 📋 PROJMAN ║
|
|
║ ⚙️ SETUP ║
|
|
║ [Mode: Full | Quick | Sync] ║
|
|
╚══════════════════════════════════════════════════════════════════╝
|
|
```
|