From cf-powers
Reviews technical analysis, design docs, or specs as a Business Analyst, verifying requirements completeness, user workflows, edge cases, and business logic.
npx claudepluginhub cloudfieldcz/cf-powers --plugin cf-powersThis skill uses the workspace's default tool permissions.
Review a technical analysis or specification document from a business analyst perspective. Focus on whether the document completely and correctly captures business requirements, user workflows, and edge cases.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Review a technical analysis or specification document from a business analyst perspective. Focus on whether the document completely and correctly captures business requirements, user workflows, and edge cases.
Announce at start: "I'm reviewing this document as a Business Analyst."
docs/plans/YYYY-MM-DD-<topic>.md)Structure your review exactly like this:
# BA Review: <topic>
## Summary
[1-2 sentence overall assessment]
## Requirements coverage
- ✅ [Requirement that is well covered]
- ❌ [Missing or incomplete requirement -- explain what's missing]
## User workflows
- ✅ [Workflow that is complete and consistent]
- ❌ [Workflow gap or inconsistency]
## Uncovered edge cases
- ❌ [Edge case 1 -- what could go wrong]
- ❌ [Edge case 2 -- boundary condition]
## Business logic questions
1. [Question about business rule or assumption]
2. [Clarification needed about behavior]
## Phase evaluation
- Phase 1: [Assessment -- is it a viable MVP?]
- Phase 2: [Assessment -- correct priority?]
## Recommendations
1. [Actionable recommendation]
2. [Actionable recommendation]
## Verdict
**Analysis quality:** [Complete / Needs revision / Major gaps]
**Recommended next step:** [Proceed to planning / Incorporate feedback / Needs rework]