skills

Generate compact, unambiguous FPF-structured output at F4-F5 formality level. Use when writing for AI agent consumers or FPF-literate humans where token economy and auditability matter: diagnostics, architecture decisions, code reviews, status reports, trust assessments, system compositions. Replaces verbose prose (F0) with typed-slot notation (~65% token savings, lossless). Do NOT use for: casual chat, teaching, non-technical audiences, creative tasks.

First Principles Framework core patterns. Use when doing engineering, research, management, or mixed human/AI work. ALWAYS use as governing patterns for any DPF or LPF work. Load individual patterns from references/ as needed — never read the full spec unless doing deep audit.

Spec-Decomposer: splits monolithic framework specifications (FPF/DPF/LPF) into atomic skill reference files. Use when: decomposing a framework monolith into skill references, updating references/ after monolith changes, or setting up a new DPF/LPF skill from a monolith. Depends on fpf-core, dpf-fpf-literacy, dpf-lfw-architecture.

Business Analysis & Requirements Engineering. Use when: identifying stakeholders, eliciting or specifying requirements, prioritizing, validating, tracing, or managing requirements changes. Depends on fpf-core.

FPF Literacy & DPF Authoring. Use when: helping an agent understand the FPF/DPF/LPF stack, creating a new DPF, loading domain knowledge into an agent, distinguishing FPF-grounded answers from generic AI responses, or choosing a carrier for publication. Depends on fpf-core.

LFW Architecture. Use when: organizing the FPF/DPF/LPF workspace, deciding where to place a new framework, setting up the skill-carrier structure, or resolving LPF vs Project boundary questions. Depends on fpf-core.

Guide for deciding when to create agent skills, how to design them well, and what anti-patterns to avoid. Use when: (1) creating a new skill, (2) deciding between skills vs AGENTS.md vs MCP vs Memory, (3) reviewing an existing skill for quality, (4) unsure if a skill is needed at all.

Maintains project state in a markdown vault (tasks, dependencies, risks, key decisions, open questions, agendas, reports) from meeting transcripts, structured notes, or owner chat updates. Use when the user needs to: (1) initialize a project-vault in a new repository, (2) update project state from meeting transcripts, (3) record user dialogue briefings, (4) manage stakeholders and responsibilities, (5) generate status reports, (6) list open questions, (7) surface contradictions and risks, (8) prepare next-meeting agendas. Triggers: project state, transcripts, meeting notes, chat updates, risks, agenda, dependencies, contradictions, ADR-style decisions.

Reverse-engineer texts into a reusable structural blueprint (reverse outlining, argument mining, copy teardown). Use when the user asks to analyze a text’s thesis, hook, framework (AIDA/PAS/PASTOR/BAB), argument map, rhetoric (Ethos/Pathos/Logos), or when they want to convert “text → structure/blueprint” to reuse patterns in writing, specs, prompts, or marketing.

Structured 10-stage methodology for planning bathroom layouts with focus on ergonomics, functionality, and safety. Use when planning bathroom furniture placement, optimizing bathroom space, arranging bathroom fixtures (toilet, sink, bathtub, washing machine), or solving bathroom layout challenges. Applicable to large bathrooms (10+ square meters) with flexible plumbing.

Structured 7-stage methodology for planning wardrobe/closet organization based on First Principles Framework. Use when organizing closet space, planning wardrobe storage, arranging clothing and accessories, optimizing closet layout, or solving wardrobe organization challenges.