Template

Files

lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

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

2026-02-06 14:52:11 -05:00

1.7 KiB

Raw Blame History

description, agent

description	agent
Discover, analyze, and charter a new project	planner

/project initiation

Purpose

Analyze an existing codebase or system description, create a project charter, and decompose into epics.

Skills Required

skills/source-analysis.md — analysis framework
skills/project-charter.md — charter template and naming
skills/epic-conventions.md — epic decomposition rules
skills/wiki-conventions.md — page naming and dependency headers
skills/visual-output.md — output formatting

Workflow

Step 1: Source Analysis

If a source codebase path is provided, analyze it using skills/source-analysis.md:

Identify tech stack, architecture, features, data model, quality state
If no source provided (greenfield), skip to Step 2

Step 2: Project Charter

Create wiki page Project: {Name} following skills/project-charter.md:

Set status to Initiating
Fill Vision, Scope (In/Out), Source Analysis Summary (if applicable)
Leave Architecture Decisions, Epic Decomposition, Roadmap as placeholders

Step 3: Epic Decomposition

Using analysis results, decompose project into epics per skills/epic-conventions.md:

Create Epic/* labels if they don't exist (check with list_labels)
Fill the Epic Decomposition table in the charter

Step 4: Present and Confirm

Show the charter to the user. Wait for approval before proceeding to /project plan.

Output

Wiki page: Project: {Name}
Labels: Epic/* labels created in Gitea
State: Initiating — awaiting /project plan

DO NOT

Create sprint issues — that's /sprint plan
Create WBS or roadmap — that's /project plan
Make architecture decisions — suggest ADRs via /adr create
Skip user approval of the charter

1.7 KiB Raw Blame History