fpf-problem-solving
From the author
Use First Principles Framework (FPF) to decompose problems, architect systems, evaluate alternatives, define quality, qualify and develop methods, initiate inquiry from ordinary work, disambiguate agent-relative instructions, steer or resume work, surface applicable methods, coordinate development states, bridge domain terms, screen mandatory steps, compare configurations, probe capability, decide under uncertainty, reconsider decisions after their basis changes, establish causality, control-loop reasoning, reason about time, synthesize ontologies, govern ontic admission, publish views, revalidate sources, select representations, use checklists, and appraise advice. Triggers: FPF, bounded contexts, SoTA packs, assurance calculus, decision theory, operational parsimony, causal/temporal reasoning, architecture, modularity, transformation flows, structural adequacy, cultural evolution, lexical discipline, Parts A-I. Not for simple task planning, general philosophy, or Agile unrelated to FPF.
Install
npx skills add CodeAlive-AI/ai-driven-development --skill fpf-problem-solving -a claude-code
Installs to .claude/skills/fpf-problem-solving/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 78
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- principle-foundational-thinkingmichael-denyer/pstack-claudeApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.Writing★ 3.4K
- first-principles-reviewGanyuanRan/AegisUse when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.Engineering★ 1.4K
- architecture-feature-firstevanca/flutter-ai-rulesUse when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.Planning★ 660
- evidence-first-engineeringNocodeMrLi/mini-program-engineering-skill-suiteApply evidence-first engineering discipline to any agent-built software project: fact discovery before action, evidence-calibrated status reporting, explicit change boundaries and stage gates, controlled confirmation for risky or external actions, sensitive-information redaction for anything shared publicly, and resumable continuity after interruptions. Use when users ask an agent to take over an existing codebase, deliver a feature across stages, verify whether work is actually complete, judge release readiness, or keep conclusions honest about what is proven versus assumed. This foundation skill is domain-neutral; vertical suites (for example mini-program engineering) build on it by adding domain facts and platform rules.Other★ 91
- design-firstrohitg00/skillkitGuides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off analyses. Use when the user asks to plan a feature, architect a system, design an API, explore implementation approaches, or requests a technical design or spec before coding — especially for complex features involving multiple components, ambiguous requirements, or significant architectural changes.Design★ 1.6K
- fable-methodSahir619/fable-methodA step-by-step problem-solving loop (classify the ask, define done, gather evidence, decide, act surgically, verify by observation, report outcome-first). Use when the user says "/fable-method", "use the fable method", or "approach this like Fable", or proactively when starting any multi-step task that no task-specific skill covers. Subcommands - plan (stop after the plan), audit (grade finished work against the loop), report (rewrite an answer outcome-first).Planning★ 2.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in