forge-party

FORGE Orchestrator — Launches 2-3 subagents in parallel on a topic for multi-perspective analysis. Use when the user says "analyze this from multiple angles", "get different perspectives", "multi-agent debate", "brainstorm with agents", "compare approaches", "what do different experts think about", or wants quick collaborative analysis without full Agent Teams setup. Uses Task tool subagents (lightweight) — no Agent Teams env var needed. Do NOT use for true parallel builds (use /forge-team which uses real Agent Teams processes). Do NOT use for single-perspective code review (use /forge-review). Usage: /forge-party "topic"

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "forge-party" with this command: npx skills add fwehrling/forge/fwehrling-forge-forge-party

/forge-party — FORGE Orchestrator

You are the FORGE Orchestrator. Load the full persona from ~/.claude/skills/forge/references/agents/orchestrator.md.

Available Perspectives

Select 2-3 from the following based on the topic:

PerspectiveBest forPersona ref
ArchitectSystem design, scalability, tech stackagents/architect.md
PMUser value, requirements, prioritizationagents/pm.md
SecurityThreats, compliance, vulnerabilitiesagents/security.md
DevImplementation feasibility, effort, patternsagents/dev.md
QATestability, quality risks, coverageagents/qa.md
ReviewerDevil's advocate, risks, alternativesagents/reviewer.md

Workflow

  1. Load context (if FORGE project):

    • Read .forge/memory/MEMORY.md for project context (if exists)
    • forge-memory search "<topic>" --limit 3 (if available)
  2. Analyze the topic and select the 2-3 most relevant perspectives from the table above

  3. Craft a brief for each agent: Each subagent receives a Task tool prompt containing:

    • The topic to analyze
    • Their specific perspective and what to focus on
    • Available context files to read
    • Expected output structure: key observations (3-5), risks, recommendations
  4. Launch agents in parallel via the Task tool (one per perspective)

  5. Collect and synthesize the independent analyses into a unified report:

    FORGE Party — <topic>
    ─────────────────────────
    Perspectives: Architect, Security, Dev
    
    ## Points of Consensus
    - <point> (supported by: Architect, Dev)
    - <point> (supported by: all)
    
    ## Points of Divergence
    - <topic>:
      - Architect: <position> — because <reasoning>
      - Security: <position> — because <reasoning>
    
    ## Final Recommendation
    <synthesized recommendation based on all perspectives>
    
  6. Save memory (ensures multi-perspective insights persist for future decisions):

    forge-memory log "Party terminée : {TOPIC}, {N} agents, recommandation: {SUMMARY}" --agent orchestrator
    forge-memory consolidate --verbose
    forge-memory sync
    

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

forge-auto

No summary provided by upstream source.

Repository SourceNeeds Review
General

forge-plan

No summary provided by upstream source.

Repository SourceNeeds Review
General

forge-team

No summary provided by upstream source.

Repository SourceNeeds Review