crowi-role-planner

Initializes the planner role session by restoring inbox, specs, and role contracts.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-role-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-role-planner
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-role-planner
Command: npx skills add https://github.com/crowi/crowi --skill crowi-role-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When starting or restarting a session as the planner role in the crowi project, context is lost: pending messages, in-progress specs, and role responsibilities must be manually reconstructed. This Skill automates that one-time startup ritual so the planner role is fully restored in a single command.

Core Features & Use Cases

  • Role establishment: Runs the agmsg actas procedure to register the session as planner and re-subscribe the message monitor.
  • Inbox and state recovery: Executes inbox.sh crowi planner to surface requests from the manager and reports from implementers, then lists .feature-state/specs/ to identify in-progress specs.
  • Role contract enforcement: Declares what the planner does (design investigation, spec/RFC writing, adversarial review convergence, handoff to manager) and does not do (kickoff, worktree implementation, git push).
  • Use Case: After a /clear or new session, run this Skill once to restore the planner identity, review pending messages, and get a status summary before receiving design instructions.

Quick Start

Start this session as the crowi planner role and report my inbox and in-progress specs.

Frequently Asked Questions about crowi-role-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a planner role session in the crowi project?

Run the crowi-role-planner skill once at session start. It executes the agmsg actas procedure to register as planner, checks the inbox via inbox.sh, lists specs in .feature-state/specs/, and reports a status summary before awaiting instructions.

What does the planner role do in a multi-agent workflow?

The planner investigates design requests, writes and converges specs/RFCs through adversarial review, then hands finished specs to the manager via agmsg. It does not run kickoff, implement in worktrees, integrate code, or push to git.

How does session restart recovery work with agmsg?

The skill re-runs the actas procedure to re-establish the planner identity and monitor subscription, then reads inbox messages and history.sh output. Handoff entries written to memory by the previous session are picked up during the spec survey step.

Why does re-running a review workflow return cached results?

Workflow calls with identical scriptPath and args are cached within a session. To force re-execution, add cache-busting fields like _round or _note, and move stale review_* artifacts in .reviews/codex-runs/<slug>/ to a _stale directory first.

When should the planner publish a spec to the wiki?

Only when the user explicitly requests it. Publishing follows a two-step Write-then-Read procedure and requires the local dev API running so the MCP endpoint at localhost:4301 is reachable.