studio-planner

Plugin studio-planner from marketplace astra-studio in Ameng2001/astra-studio-plugins. Commands read from the repo's manifest — 6 days ago.

Skills (5)

• build-skills

  Generate initial skill implementations in the target plugin directory after spec generation. Produces working first drafts that need iterative refinement through testing and skill-creator. Use when the user has confirmed the build stage. Works for both create and modify iterations.

• domain-model

  Analyze event storm results to identify business domains, draw plugin boundaries, and map relationships between them. Use after event-storm, when you have a set of events and processes and need to decide how many plugins to build and what each one owns. Produces a domain map with plugin candidates.

• event-storm

  Run a multi-role brainstorming session to discover business events, user journeys, pain points, and processes. Use when starting a new plugin project, exploring a business domain, or when someone says "let's brainstorm" or "help me figure out what to build". Produces a structured event storm with pe

• skill-design

  Design the skill breakdown for a plugin — enumerate skills, map data flow, assess complexity, and plan implementation. Use after domain-model when you have plugin candidates and need to decide what individual skills each plugin should contain. Produces a skill map with dependencies and complexity ti

• spec-generate

  Generate all plugin specification files from planning artifacts — SKILL.md skeletons, plugin.json.draft, brief.md, and commands. Use after skill-design when the skill map is ready and you want to produce the complete workspace that the build stage can consume. Pure automation, no interactive input n

Slash commands (1)

• /studio-planner:plan

  Plan a new plugin — brainstorm, model domains, design skills, generate specs, build initial drafts

Subagents (3)

• {{EXPERT_SLUG}}

  {{One-line summary of this expert's domain and when to invoke them for review. TEMPLATE: fill in all {{...}} placeholders when creating a real expert.}}

• architect

  Software architect for plugin planning sessions. Invoke to review structure, boundaries, and long-term sustainability of a design — where plugin boundaries fall, what is over- or under-engineered, and whether the design holds up as the system grows.

• product-manager

  Product manager for plugin planning sessions. Invoke to review a design from the user's point of view — who the users really are, whether it solves a real problem, and where technical elegance is not serving user needs.

Similar plugins