ftm-intent

Generate and update hierarchical INTENT.md documentation across modules.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-intent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ftm-intent
Source: https://github.com/kkudumu/feed-the-machine/tree/main/ftm-intent
Command: npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-intent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps code reviews aligned with actual implementation by generating and updating a hierarchical INTENT.md documentation layer across the repository.

Core Features & Use Cases

  • Bootstrap the root INTENT.md and per-module INTENT.md files by analyzing the codebase.
  • Incremental updates after commits to keep module intent in sync with changes.
  • Optional graph-powered mode via .ftm-map for faster, consistent intent generation.

Quick Start

Execute the ftm-intent skill to bootstrap and maintain the INTENT.md documentation layer across the repository.

Frequently Asked Questions about ftm-intent

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

FAQPage Schema
What is an INTENT.md file and how does it help with code reviews?

An INTENT.md file documents the intent behind code using a Does/Why/Relationships/Decisions template. It keeps code reviews aligned with actual implementation by exposing per-exported-function entries for governance and review.

How do I generate hierarchical documentation for my project modules?

You can generate hierarchical module documentation by bootstrapping a root INTENT.md and per-module files. The skill analyzes the codebase to create this documentation layer automatically.

How do I keep code documentation in sync after commits?

To keep code documentation in sync after commits, use incremental mode. This updates existing INTENT.md files to reflect module changes without regenerating the entire hierarchy.

Can I use a graph-powered approach for faster intent generation?

Yes, you can enable graph-powered intent generation via the .ftm-map file. This optional mode provides faster and more consistent INTENT.md updates across the repository.

Does the intent documentation template work for existing repositories?

Yes, it works for existing repositories. When INTENT.md is absent, it operates in bootstrap mode to create files; when present, it uses incremental mode to update existing documentation.

What is the best way to document code intent for governance?

The best way to document code intent for governance is using the Does/Why/Relationships/Decisions template within a hierarchical INTENT.md layer. This exposes per-exported-function entries to support structured code reviews.