persona-ford-parsons

Evaluate architectural plans for evolvability, coupling, and fitness functions.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/smp4/claude-skills --skill persona-ford-parsons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-ford-parsons
Source: https://github.com/smp4/claude-skills/tree/main/docs/dev/ideas/personas/persona-skills-context/ford-parsons-persona
Command: npx skills add https://github.com/smp4/claude-skills --skill persona-ford-parsons

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill channels Neal Ford and Rebecca Parsons to reveal hidden coupling, undocumented fitness functions, and irreversible bets that could undermine a plan’s evolvability, turning vague architectural promises into actionable critique.

Core Features & Use Cases

  • Persona-driven review: Run review mode against plans or specs to identify fitness function gaps, unjustified coupling, and implicit bets using the persona’s heuristics.
  • Construction guidance: When generating designs or ADRs, follow the persona’s construction protocol to name fitness criteria, map coupling, and document the bets being placed on future change.
  • Reference-backed protocol: Use the included references/review.md and references/construction.md to anchor findings in the structured Ford/Parsons workflows.

Quick Start

Ask for an evolutionary architecture critique of your plan from Neal Ford and Rebecca Parsons.

Frequently Asked Questions about persona-ford-parsons

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate architectural plans for evolvability and hidden coupling?

Evaluating architectural plans for evolvability requires surfacing hidden coupling, undocumented fitness functions, and irreversible bets. A persona-driven review applies specific heuristics to identify these structural risks, turning vague architectural promises into actionable critique.

What are fitness functions in evolutionary architecture and when do I need to define them?

Fitness functions in evolutionary architecture are measurable criteria that validate architectural intent. You need to define them during plan reviews and spec inspections when long-term coupling and system evolvability are in question, ensuring future changes remain verifiable.

How do I document implicit bets and coupling rationale in an Architecture Decision Record?

Documenting implicit bets and coupling rationale in an ADR follows a construction protocol that maps dependencies, names fitness criteria, and records the bets placed on future change. This ensures architectural decisions are transparent and reversible where possible.

Does this architectural review approach work for interview outputs and new plan generation?

This architectural review approach works for interview outputs, new plan generation, and spec inspections. It applies evolutionary architecture heuristics to any phase where fitness functions, coupling rationale, and implicit bets need surfacing.

What is the best way to stress-test a software architecture for reversibility?

The best way to stress-test a software architecture for reversibility is running a structured review protocol that identifies irreversible bets and hidden coupling. This surfaces undocumented fitness functions and maps coupling rationale to ensure long-term evolvability.

Why does my architectural plan fail to address long-term coupling and evolvability concerns?

Architectural plans fail to address long-term coupling when they lack documented fitness functions and contain implicit bets. A structured review surfaces these undocumented elements, mapping coupling rationale to reveal irreversible decisions that undermine evolvability.