project-orchestrator:brainstorming

Generate cross-service design documents and implementation tasks with status tracking.

Updated Feb 15, 2026

Search Tags:#design #brainstorming #orchestration #project-management #multi-service #living-state

Ready to run

npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-brainstorming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-orchestrator:brainstorming
Source: https://github.com/GigaFyde/project-orchestrator/tree/main/skills/brainstorming
Command: npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seamless coordination of feature ideas into cross-service designs and executable plans, preserving context across sessions and agent teams.

Core Features & Use Cases

End-to-end lifecycle: brainstorm → design → implement → review → finish, all in one skill.
Living design artifacts: generates and updates living state documents that survive session resets.
Config-driven scoping: reads project.yml to determine services, plans, and architecture references; asks clarifying questions when needed.
Team orchestration: supports single-service exploration or multi-service brainstorming with designated design perspectives.

Quick Start

Ask Claude to load the project configuration and start a brainstorming session with /project:brainstorming to generate a design plan.

Frequently Asked Questions about project-orchestrator:brainstorming

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

FAQPage Schema

How do I coordinate cross-service design and implementation tasks for a monorepo?▼

Cross-service design coordination is handled by validating project configuration and generating persistent plan artifacts on disk. It tracks feature status from brainstorming through completion, preserving context across sessions and agent teams.

What is the best way to maintain living design documents for feature lifecycles across multiple services?▼

Living design documents are generated and updated as persistent state files that survive session resets. The skill manages the end-to-end lifecycle from brainstorm to finish, ensuring context is preserved for multi-service architecture.

Do I need a project.yml configuration file to start multi-service brainstorming?▼

A project.yml configuration file is required to determine services, plans, and architecture references. The skill reads this file to scope the brainstorming session and will ask clarifying questions when needed.

Can I use this skill for single-service feature exploration or is it strictly for multi-service projects?▼

Single-service feature exploration is fully supported alongside multi-service brainstorming with designated design perspectives. The skill adapts to the scope defined in your project configuration.

How does two-stage review work for cross-service feature implementation?▼

Two-stage reviews are integrated into the feature lifecycle from design to implementation. The skill generates plan artifacts in the configured plans directory and tracks status through brainstorming, designing, implementing, and completing phases.

What are the limitations of using on-disk persistent state for project orchestration?▼

On-disk persistent state requires a monorepo environment with multiple services and a valid project.yml. It is specifically designed for cross-service design coordination and two-stage reviews rather than simple single-file tasks.