Help us improve
Share bugs, ideas, or general feedback.
From flow
Provides advocate, critic, and neutral stance prompts for multi-perspective analysis of tradeoffs, risks, decisions, and blind spots in code development.
npx claudepluginhub cofin/flow --plugin flowHow this skill is triggered — by the user, by Claude, or both
Slash command
/flow:perspectivesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Shared prompt library for structured multi-perspective analysis. Provides stance prompts (advocate, critic, neutral) and critical thinking frameworks used by other Flow skills.
Evaluates decisions via stance rotation (neutral, advocate, critic perspectives), synthesizes confidence-rated recommendation with next steps. For architectural choices, tech options, build-vs-buy, tradeoffs.
Assembles stakeholder perspectives to deliberate complex architectural, technology, or design decisions before brainstorming, surfacing tensions and convergences without forcing choices.
Deep reasoning for complex decisions — expert panel simulation, devil's advocate, what-if scenarios, and structured tradeoff analysis. Use when a decision has high stakes, multiple valid approaches, or you need to stress-test your thinking. Triggers: think, think through, analyze, expert panel, devil's advocate, what if, tradeoff, decision, weigh options, stress test, second opinion.
Share bugs, ideas, or general feedback.
Shared prompt library for structured multi-perspective analysis. Provides stance prompts (advocate, critic, neutral) and critical thinking frameworks used by other Flow skills.
This skill provides the foundation that other skills build on:
Typically loaded by other skills (challenge, consensus, persona skills) rather than invoked directly. Can be invoked directly when you want raw stance prompts for custom analysis.
Proposal: Moving from a monolithic database to a distributed microservices architecture.
Advocate: "Enables independent scaling of services, improves developer velocity by reducing coupling, and increases fault tolerance through isolation."
Critic: "Significantly increases operational complexity (service discovery, distributed tracing), introduces network latency between services, and requires complex distributed transaction management."
Neutral: "The transition is beneficial if the current monolith is a bottleneck for deployment frequency or horizontal scaling. However, the team must first invest in robust observability and CI/CD pipelines to manage the added overhead."