studio-docs

Astra Studio

A Claude Code plugin marketplace for planning, designing, validating, and shipping plugins.

Astra Studio handles the outer loop of plugin development — business analysis, domain modeling, plugin validation, and promotion. Individual skill authoring and testing is executed through the official skill-creator as an internal pipeline capability.

Plugins

Plugin	Skills	What it does	Install
studio-core	4	Workspace management — init, promote, status, create-expert	claude plugin install studio-core@astra-studio
studio-insight	6	Business analysis toolkit — personas, journeys, processes, domains	claude plugin install studio-insight@astra-studio
studio-planner	5	Planning pipeline — event storming, domain modeling, skill design, build orchestration	claude plugin install studio-planner@astra-studio
studio-quality	2	Quality assurance — plugin validation, MCP wiring	claude plugin install studio-quality@astra-studio

Quick Start

# 1. Register the marketplace
claude plugin marketplace add github:VanLengs/astra-studio-plugins

# 2. Install what you need
claude plugin install studio-core@astra-studio
claude plugin install studio-insight@astra-studio
claude plugin install studio-planner@astra-studio
claude plugin install studio-quality@astra-studio

# 3. Initialize studio in your project
/studio-core:init

# 4. Plan a plugin
/studio-planner:plan "your business domain"

# 5. Confirm the build plan
# → Astra Studio generates specs, then produces initial skill drafts in {target_dir}/

# 6. Test and iterate each skill with real inputs
# → Use skill-creator to refine individual skills

# 7. Validate the plugin
/studio-quality:validate {target_dir}

# 8. Ship a version (design docs stay active for next iteration)
/studio-core:promote {plugin-name}

studio-insight: Standalone Artifact Skills

These 6 skills produce professional deliverables independently — no pipeline required:

/studio-insight:persona-insight "全职妈妈，两个孩子"    # → persona card + empathy map
/studio-insight:journey-map "日常营养管理流程"           # → journey map + emotional curve
/studio-insight:process-flow "从记录饮食到生成周报"      # → process diagram + decision points
/studio-insight:domain-canvas "儿童健康管理"             # → domain boundary map + classification
/studio-insight:behavior-matrix "儿童健康管理"           # → actor × action × event × data table
/studio-insight:opportunity-brief "儿童健康管理"         # → prioritized opportunity assessment

studio-planner: Planning Pipeline

/studio-planner:plan chains 5 pipeline skills:

Step 1: event-storm
  Multi-role brainstorming (PM, architect, domain experts)
  → Invokes: persona-insight, journey-map, process-flow
  → Identifies: KB dependencies, expert scope (planning vs runtime)
  → Writes: studio/changes/{domain}/event-storm.md

        ↓ user confirms

Step 2: domain-model
  Clusters events into business domains, draws plugin boundaries
  → Full analysis mode: invokes domain-canvas, behavior-matrix, opportunity-brief
  → Fast mode: skips insight tools, goes directly to plugin proposals
  → Writes: studio/changes/{domain}/domain-map.md
  → Creates: {target_dir}/ scaffold for each plugin candidate

        ↓ user confirms

Step 3: skill-design
  Breaks each plugin into skills with interfaces and data flow
  → Detects plugin traits: stateful, hil-gated, kb-dependent, multi-pipeline, expert-scoped
  → Assesses complexity: prompt-only / scripts / MCP
  → Writes: studio/changes/{plugin}/skill-map.md (includes traits + pipelines)

        ↓ user confirms

Step 4: spec-generate
  Auto-generates specification files + trait-conditional scaffolding
  → Design docs → studio/changes/ (brief.md, plugin.json.draft)
  → Implementation → {target_dir}/ (SKILL.md skeletons, commands)
  → If stateful: init-workspace skill + runtime config/status templates
  → If hil-gated: approval gate sections in relevant skills
  → If multi-pipeline: per-pipeline orchestration commands
  → Advances status: planning → building

Step 5+: build, test, validate, promote
  build-skills produces initial skill drafts via skill-creator (working first drafts)
  → Test each skill with real inputs, iterate with skill-creator
  /studio-quality:validate validates {target_dir}/ and advances to approved
  /studio-core:promote creates a versioned milestone (v0.1 → v0.2)
  → Design docs are snapshotted to archive but stay active for next iteration

Subagent Roles

Both studio-insight and studio-planner use multiple perspectives via subagent roles: