feat: major improvements to projman plugin v1.0.0

- Remove Wiki.js MCP server entirely
- Add wiki, milestone, and dependency tools to Gitea MCP server
- Add parallel execution support based on dependency graph
- Add mandatory pre-planning validations (org check, labels, docs/changes)
- Add CLI blocking rules to all agents (API-only)
- Add standardized task naming: [Sprint XX] <type>: <description>
- Add branch naming convention: feat/, fix/, debug/ prefixes
- Add MR body template without subtasks
- Add auto-close issues via commit keywords
- Create claude-config-maintainer plugin for CLAUDE.md optimization
- Update all sprint commands with new tools and workflows
- Update documentation to remove Wiki.js references

New MCP tools:
- Wiki: list_wiki_pages, get_wiki_page, create_wiki_page, create_lesson, search_lessons
- Milestones: list_milestones, get_milestone, create_milestone, update_milestone
- Dependencies: list_issue_dependencies, create_issue_dependency, get_execution_order
- Validation: validate_repo_org, get_branch_protection, create_label

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-19 17:10:22 -05:00
parent d84425cbb0
commit 74b28170fa
39 changed files with 3410 additions and 4023 deletions

View File

@@ -1,10 +1,10 @@
---
description: Run initial setup for support-claude-mktplace
description: Run initial setup for projman plugin
---
# Initial Setup
Run the installation script to set up the toolkit.
Run the installation script to set up the projman plugin.
## What This Does
@@ -12,7 +12,9 @@ Run the installation script to set up the toolkit.
2. Installs all dependencies
3. Creates configuration file templates
4. Validates existing configuration
5. Reports remaining manual steps
5. Validates repository organization
6. Syncs label taxonomy
7. Reports remaining manual steps
## Execution
@@ -21,13 +23,92 @@ cd ${PROJECT_ROOT}
./scripts/setup.sh
```
## Configuration Structure
The plugin uses a hybrid configuration approach:
**System-Level (credentials):**
```
~/.config/claude/gitea.env
```
Contains API credentials that work across all projects.
**Project-Level (repository/paths):**
```
project-root/.env
```
Contains project-specific settings like repository name.
## After Running
Review the output for any manual steps required:
- Configure API credentials in `~/.config/claude/`
- Run `/labels-sync` to sync Gitea labels
- Verify Wiki.js directory structure
1. **Configure API credentials** in `~/.config/claude/gitea.env`:
```
GITEA_URL=https://gitea.your-company.com
GITEA_TOKEN=your-api-token
GITEA_ORG=your-organization
```
2. **Configure project settings** in `.env`:
```
GITEA_REPO=your-repo-name
WIKIJS_PROJECT=your-project
```
3. **Run `/labels-sync`** to sync Gitea labels
4. **Verify Gitea Wiki** is accessible and has proper structure
## Pre-Flight Checks
The setup script validates:
- Repository belongs to an organization (required)
- Required label categories exist
- API credentials are valid
- Network connectivity to Gitea
## Re-Running
This command is safe to run multiple times. It will skip already-completed steps.
## MCP Server Structure
The plugin bundles these MCP servers:
```
plugins/projman/mcp-servers/
└── gitea/
├── .venv/
├── requirements.txt
└── mcp_server/
├── server.py
├── gitea_client.py
└── tools/
├── issues.py
├── labels.py
├── wiki.py
├── milestones.py
└── dependencies.py
```
## Troubleshooting
**Error: Repository not under organization**
- This plugin requires repositories to belong to a Gitea organization
- Transfer your repository to an organization or create one
**Error: Missing required labels**
- Run `/labels-sync` to create missing labels
- Or create them manually in Gitea
**Error: Cannot connect to Gitea**
- Verify `GITEA_URL` in `~/.config/claude/gitea.env`
- Check your API token has proper permissions
- Ensure network connectivity
**Error: Virtual environment creation failed**
- Ensure Python 3.8+ is installed
- Check disk space
- Try running `python -m venv .venv` manually in the MCP server directory