Communitygithub.com

adulari/forge

Fast, model-agnostic AI coding harness and CLI in Rust — routes every task to the optimal model for cost × capability.

¿Qué es forge?

forge is a Claude Code agent skill that fast, model-agnostic AI coding harness and CLI in Rust — routes every task to the optimal model for cost × capability.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add adulari/forge

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Council — Multi-Perspective Analysis

A multi-perspective analysis framework that provides objective, debiased evaluation of codebases, projects, and documentation. Uses multiple viewpoints and debiasing techniques to overcome the tendency to anchor on existing code.

The Problem This Solves

AI tools (and humans) tend to anchor on existing code. They see what IS and struggle to imagine what COULD BE. They validate rather than explore. Council uses:

  1. Debiasing techniques — Methods that force fresh thinking
  2. Multiple perspectives — Different mental models that catch different things
  3. Structured synthesis — Combining insights while tracking disagreements

When to Use

  • Evaluating if current approach is still optimal
  • Exploring alternatives to existing implementation
  • Identifying hidden assumptions in your project
  • Getting objective feedback before major decisions
  • When stuck in local optimum
  • When you suspect there might be a better way but can't see it
  • When AI tools keep echoing back your existing patterns

Input

User provides:

  • Target: Repository path, documentation, or specific problem description
  • Goal (optional): What success looks like (e.g., "maximize profitability")
  • Constraints (optional): What must be preserved (e.g., "must use existing data model")

Execution Flow

Phase 1: Scout

Read and understand the target thoroughly. Document:

  • What the project does
  • How it's currently structured
  • What constraints exist
  • What the stated goals are

Do NOT form opinions yet. Just gather facts.

Phase 2: Generate Perspectives

Select 3-5 relevant perspectives based on the target:

PerspectiveFocusBest For
ArchitectStructure, patterns, coupling, cohesionSystem design, refactoring
ChallengerAssumptions, risks, alternativesDecision validation, risk mitigation
OpportunistNew tech, shortcuts, simplificationOptimization, debt reduction
SecurityTrust boundaries, failure modesSafety, reliability
EconomistCost, complexity, ROIResource allocation, prioritization
UserUsability, value, frictionUX, product decisions
ArchaeologistLegacy, debt, historyUnderstanding, migration
FuturistTrends, scaling, evolutionLong-term planning

For complex targets, use spawn_agents to run perspectives in parallel — each agent works independently to avoid groupthink, then results combine in Phase 3.

For simpler targets, run perspectives sequentially in a single agent.

Each perspective applies these debiasing techniques:

  1. Fresh Eyes Mode: Deliberately ignore the existing implementation. Ask: "What would I build if starting from zero, knowing only the goal?"
  2. Challenge Mode: Question every assumption. Why does this component exist? What if we removed it? What if the opposite were true?
  3. Rebuild Mode: "If I had to solve this from scratch with today's knowledge, what would I do differently?"

See references/debiasing.md for detailed debiasing techniques and prompts.

Phase 3: Synthesize

Combine perspectives into structured output:

  1. Agreements: What multiple perspectives agree on (high confidence)
  2. Disagreements: Where perspectives conflict (dig deeper — these reveal tradeoffs)
  3. Novel Insights: Things only one perspective caught
  4. Prioritized Recommendations: Ranked by impact and confidence

See agents/synthesizer.md for detailed synthesis instructions when using subagents.

Phase 4: Validate

  • Check that recommendations don't contradict each other
  • Flag any assumptions that weren't validated
  • Identify what information would change conclusions

Output Format

# Council Report: [Target]

## Executive Summary
[2-3 sentence objective assessment — not a summary of what was done, but a verdict]

## Key Findings

### [Finding Name]
- **What**: [Clear description of the finding]
- **Perspectives that agree**: [List]
- **Perspectives that disagree**: [List + brief reason]
- **Confidence**: [High/Medium/Low]
- **Evidence**: [Specific file:line, metric, or observation]

## Recommendations

### [HIGH IMPACT] [Recommendation Title]
- **Problem addressed**: [The finding this fixes]
- **Solution**: [Concrete action]
- **Expected impact**: [What improves and by how much]
- **Effort**: [Low/Medium/High]
- **Risk**: [Low/Medium/High]
- **Perspectives supporting**: [List]

### [MEDIUM IMPACT] ...

### [LOW IMPACT] ...

## Alternative Approaches Considered

| Approach | Pros | Cons | Verdict |
|----------|------|------|---------|
| ...      | ...  | ...  | Keep/Replace/Explore further |

## What Would Change This Assessment
- If [X] is true, then [recommendation Y changes]
- [Unvalidated assumption that matters]

Bundled Resources

  • references/debiasing.md — Detailed debiasing techniques and prompts per perspective type
  • agents/perspective.md — Instructions for subagents running individual perspective analyses
  • agents/synthesizer.md — Instructions for a synthesis subagent combining multiple perspective outputs

Skills relacionados