| name | fpf-review |
| description | Triggers: architecture review, FPF, functional programming framework, systems architecture
Architecture review using FPF (Functional Programming Framework) methodology.
Evaluates codebases through functional, practical, and foundation perspectives.
Use when: conducting architecture reviews, evaluating system design
DO NOT use when: simple code reviews, bug fixes, documentation updates
|
| category | review-methodology |
| tags | ["architecture","review","FPF","functional","systems-design"] |
| dependencies | ["pensive:code-reviewer","imbue:review-core"] |
| tools | ["Read","Grep","Glob","TodoWrite"] |
| usage_patterns | ["architecture-analysis","design-evaluation","recommendation-generation"] |
| complexity | advanced |
| estimated_tokens | 3000 |
| modules | ["modules/functional-perspective.md","modules/practical-perspective.md","modules/foundation-perspective.md"] |
FPF Architecture Review
Conduct architecture reviews using the FPF (Functional Programming Framework) methodology, evaluating codebases through three complementary perspectives.
Philosophy
Architecture reviews should be systematic and multi-dimensional. FPF provides three lenses:
- Functional: What the system does (capabilities, behaviors)
- Practical: How well it works (performance, usability)
- Foundation: What it's built on (principles, patterns)
This lighter skill-based approach replaces heavyweight tooling with focused analysis.
Quick Start
/fpf-review
/fpf-review --perspective functional
/fpf-review --perspective practical
/fpf-review --perspective foundation
/fpf-review --scope plugins/sanctum
The Three Perspectives
1. Functional Perspective
Question: What does this system do?
Evaluates:
- Feature completeness
- Capability coverage
- Behavior correctness
- Integration points
Outputs:
- Feature inventory
- Capability gaps
- Behavior anomalies
2. Practical Perspective
Question: How well does this system work?
Evaluates:
- Performance characteristics
- Usability patterns
- Operational concerns
- Scalability considerations
Outputs:
- Performance assessment
- Usability issues
- Operational recommendations
3. Foundation Perspective
Question: What is this system built on?
Evaluates:
- Architectural patterns
- Design principles
- Code quality
- Technical debt
Outputs:
- Pattern analysis
- Principle adherence
- Debt inventory
Workflow
Phase 1: Discovery (fpf-review:discovery-complete)
- - Identify components, modules, layers
