fmcf

Implements the Fibonacci Matrix Context Flow governance model for wiki-first software architecture development.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/chrismichaelps/skills --skill fmcf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fmcf
Source: https://github.com/chrismichaelps/skills/tree/main/skills/fmcf
Command: npx skills add https://github.com/chrismichaelps/skills --skill fmcf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

FMCF (Fibonacci Matrix Context Flow) solves the problem of maintaining high-performance and disciplined architectural development by ensuring all code is a faithful projection of a comprehensive and interlinked Obsidian-style wiki vault.

Core Features & Use Cases

  • Wiki-first Development: Requires a complete wiki page for every module before code is written.
  • Governance Framework: Provides a comprehensive set of laws and best practices for maintaining architecture integrity.
  • Role-based Collaboration: Defines clear roles (Architect, DNA Engineer, Shadow, Forensic Guardian) for collaborative development.
  • Autonomous Decision Making: Employs 'grillme' protocol for resolving design questions automatically.
  • Continuous Handoff: Ensures zero-loss continuity through handoff pages during role transitions and session breaks.
  • Use Case: Ideal for initializing a new FMCF project, governing existing projects, authoring the wiki, and preventing context toxicity during development.

Quick Start

Initialize FMCF on your project and start building the Obsidian-style wiki vault to guide your code development.

Frequently Asked Questions about fmcf

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

FAQPage Schema
What is wiki-first governance for software architecture?

Wiki-first governance requires a comprehensive, interlinked Obsidian-style wiki vault to serve as the single source of truth before any code is written, ensuring disciplined architectural development at scale.

How do I prevent context toxicity during agile development?

You prevent context toxicity by implementing the FMCF governance model, which uses role-based workflows, continuous handoff pages, and autonomous design decision protocols to maintain zero-loss continuity during session breaks.

Do I need an Obsidian vault to govern architectural development at scale?

Yes, you need a well-defined Obsidian-style wiki vault acting as the single source of truth, where a complete wiki page must exist for every module before code implementation begins.

How do I resolve design questions automatically in software development?

You resolve design questions automatically by employing the 'grillme' protocol, an autonomous design decision-making mechanism defined within the FMCF governance framework.

What roles are defined for collaborative architectural development?

The framework defines clear roles including Architect, DNA Engineer, Shadow, and Forensic Guardian to establish structured, role-based collaboration and maintain architecture integrity.