Skip to main content

setup-project

Set up a new Agile-ready project with recommended states, labels, and work item types Arguments: <project-name> [--template lean|standard].

Source facts

Repository
Agents-Store/codex-plugins
Last source activity
November 1, 2026 at 02:46
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
setup-project
description
Set up a new Agile-ready project with recommended states, labels, and work item types Arguments: <project-name> [--template lean|standard].
# Setup Project Configure a new or existing Plane project with Agile-optimized states, labels, work item types, and features. Method and rules: the `plane-ops:project-setup` skill. ## Arguments Format: `<project-name> [--template lean|standard]` - project-name: Name of the project (required) - --template: Configuration template (default: lean) - lean: Minimal setup for 1-3 person teams - standard: Full Agile setup for 4+ person teams Parse from "$ARGUMENTS". ## Process 0. **Bootstrap connector** — consult the `connector-bootstrap` skill. Probe `ToolSearch` for the Plane resource tools referenced below (`project`, `state`, `label`, `workitem_type`, `project_estimate`); their names are `mcp__<server>__<resource>`, never assume a specific MCP prefix. If multiple Plane instances are connected, ask the user which one to use. All formulas and rules come from the `agile-fundamentals` skill. Calls are written `resource(action=..., ...)`. 1. **Create or find project:** ``` project(action=list) // check if exists (follow next_cursor) project(action=create, name=<name>, identifier="<auto-generated>") // if new ``` 2. **Enable features:** ``` project(action=update_features, project_id=<id>, cycles=true, // Sprints pages=true, // Retro notes modules=true, // Feature grouping (standard only) epics=true, // Epic tracking (standard only) views=true, // Custom views (standard only) workitem_types=true) // Story/Task/Bug/Spike (standard only) ``` 3. **Create states:** Lean: Backlog → Todo → In Progress → Done Standard: Backlog → Todo → In Progress → In Review → Done → Cancelled ``` state(action=create, project_id=<id>, name=<name>, color=<hex>, group=<backlog|unstarted|started|completed|cancelled>, sequence=<n>) ``` 4. **Create labels:** Type: bug, feature, tech-debt Status: ready, needs-refinement, blocked, retro-action Additional (standard): spike, chore, quick-win ``` label(action=create, project_id=<id>, name=<name>, color=<hex>) ``` 5. **Create work item types (standard only):** ``` workitem_type(action=resolve, project_id=<id>, name="Story") workitem_type(action=resolve, project_id=<id>, name="Task") workitem_type(action=resolve, project_id=<id>, name="Bug") workitem_type(action=resolve, project_id=<id>, name="Spike") ``` `resolve` finds or creates the named type for the project and never duplicates it. 5b. **Estimate scale (standard only, optional):** ``` project_estimate(action=create, project_id=<id>, name="Fibonacci", type="points") project_estimate(action=create_points, project_id=<id>, estimate_id=<estimate_id>, points=[{"value": "1", "key": 0}, {"value": "2", "key": 1}, {"value": "3", "key": 2}, {"value": "5", "key": 3}, {"value": "8", "key": 4}]) project_estimate(action=link, project_id=<id>, estimate_id=<estimate_id>) ``` With an estimate system, work items carry `estimate_point` ids (see the `estimation` skill). 6. **Verify setup:** ``` state(action=list, project_id=<id>) label(action=list, project_id=<id>) project(action=get_features, project_id=<id>) ``` Confirm everything is configured. ## Example Usage ``` /setup-project "My Startup App" /setup-project "Enterprise Platform" --template standard ```
View on GitHub