feature-map

---

English

feature-map helps Claude Code and Codex keep cross-layer business behavior consistent. It maps the files that belong to the same business flow, reminds the agent when one touchpoint changes, and gives you an audit path before silent drift becomes a production bug.

Most code tools understand imports, callers, and symbols. Real product bugs often live somewhere else:

• a mobile form changed, but backend validation did not
• an admin approval page still shows the old status
• API docs promise a field that the service no longer accepts
• a payment rule changed, but reporting, notifications, and migration logic stayed behind

feature-map exists for that semantic layer.

Available For

Agent	Status	What it can do
Claude Code	Available	Native plugin commands, PostToolUse reminders, pre-commit sync checks
Codex	Available	Skill adapter, flow audit workflow, registry helpers, shared source of truth

The Claude plugin and Codex skill use the same FEATURE-MAP.yaml registry, so one project map can guide both agents.

What It Does

• Declares business flows in FEATURE-MAP.yaml
• Connects touchpoints across UI, backend, services, docs, database migrations, and event consumers
• Tracks invariants that must stay consistent across those touchpoints
• Marks flows stale when a mapped file changes
• Audits drift with GAP, DRIFT, IMPACT, RULE-GAP, and OK findings
• Flags undocumented business rules by cross-checking test-touchpoint descriptions against declared invariants
• Imports blueprint/FRD/SRS documents into draft flow maps with page evidence
• Supports multi-repo flows through a local repo registry
• Follows impact chains with declared impacts
• Uses call-graph blast radius when .code-review-graph/graph.db is present

How It Works

Why This Matters

AI agents are fast, but speed can widen the gap between files that should change together. feature-map gives agents a lightweight memory of the product's business logic, not just the code graph.

The goal is simple:

When one part of a business flow changes, the rest of the flow should not be forgotten.

This plugin is meant to grow into a shared safety layer for AI-assisted engineering: small enough to install anywhere, explicit enough to review in Git, and practical enough to help during real edits.

Quick Example

flows:
  partner-registration:
    description: "Partner signs up, gets validated, and is reviewed by admin"
    policy: "KTP is required before partner verification can be approved"
    touchpoints:
      - path: "mobile/**/PartnerRegistrationForm.*"
        role: client-form
      - path: "api/**/PartnerRegistrationController.*"
        role: backend-validation
      - path: "admin/**/PartnerVerificationPage.*"
        role: admin-view
      - path: "docs/api/partner-registration.md"
        role: docs
    invariants:
      - "KTP required/optional status must match client, backend, admin, and docs"
      - "Verification status values must be consistent across API and admin UI"

If an agent edits the mobile form, feature-map reminds it to inspect backend validation, admin verification, and API docs before calling the task done.

Claude Code Usage

Install from GitHub (recommended — works for anyone, no local clone needed):

claude plugin marketplace add ade-syofyan/feature-map
claude plugin install feature-map@feature-map