crowi-role-manager

Restores the manager role session state, watchers, and inbox for Crowi orchestration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a Claude Code session acting as the Crowi manager restarts (via /clear, compaction, or version updates), all persistent monitors, role identity, and working context are lost. This Skill re-establishes the manager role in one pass so orchestration of worktrees, integrations, and reviews can resume without manual reconstruction.

Core Features & Use Cases

  • Role re-establishment: Runs the agmsg actas flow to register the session as manager and re-checks the inbox for planner handoffs, reviewer verdicts, and impl completion reports.
  • Watcher restoration: Re-attaches the persistent orchestrate-watch.sh monitor that picks up READY_TO_INTEGRATE signals and review thresholds from worktrees.
  • State reconciliation: Reads git worktree list, .feature-state task JSON files, main-write.lock, and kickoff-chain.json to report in-progress features, pending integrations, and stale locks.
  • Use Case: After a context compaction wipes your monitors mid-project, invoke this Skill to restore the manager identity, re-arm both watchers, and get a one-line summary of inbox items and active worktrees before continuing.

Quick Start

Start a new session as the Crowi manager and run the crowi-role-manager skill to restore watchers, inbox, and worktree state.

Frequently Asked Questions about crowi-role-manager

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

FAQPage Schema
How do I restore a manager session after compaction in Claude Code?

Run the crowi-role-manager skill once at session start. It re-registers the agmsg manager identity, re-attaches the orchestrate-watch persistent monitor, checks the inbox, and reads worktree and feature-state files to rebuild context.

How do I monitor git worktrees for ready-to-integrate signals?

Launch orchestrate-watch.sh as a persistent Monitor task. It watches worktree lanes for READY_TO_INTEGRATE signal files and review thresholds, and must be re-attached after any session restart since monitors do not survive compaction.

What state files does the Crowi manager workflow use?

The workflow reads .feature-state/tasks/*.json for task status, .feature-state/main-write.lock for serialization, kickoff-chain.json for chained kickoffs, and orchestrate-state.json for the last reviewed main SHA.

Why do duplicate READY_TO_INTEGRATE signals fire after a restart?

Old watcher task IDs can survive and re-deliver the same signal after a restart. The skill warns against double-integrating the same worktree; deleting the signal file after a completed integrate stops the duplicates.

What tasks does the manager role not perform?

The manager does not write specs or RFCs (planner's role), implement in worktrees (impl's role), push to git without explicit user instruction, or commit directly to main or release branches. It also delegates flaky-test root-cause investigation to subagents.