# featkpr, in two minutes

A short, plain version of this site, for anyone. Every link below opens the part of the site that goes deeper.

**Every web app is a set of features**

Sign in, create a book, share a page, delete an account. People move through them in flows, to reach a goal.

**Almost nobody has that written down**

It lives in people's heads. Documents fall out of date, and tests only check the app one screen at a time.

**featkpr draws the map**

It reads the app's code and walks a running copy, then writes down the features, how they lead into each other, the flows people take and the goals they reach.

**Your team checks it, one question at a time**

Keep it, drop it, or say it better. Each answer is kept, with who gave it and when.

**Everything else is built on the checked map**

Tests, checks of who may do what, what a code change touches. Later: analytics, feature flags, a user guide.

One drafted goal on featkpr's Flows screen: the screens a person walks to reach it, left to right, before a person keeps or drops it. The app runs on sample data here.

Shown on BookStack, an open-source wiki we don't own: 312 features in 13 modules, 149 flows to 88 goals, read 28 Sep 2026.

## The words, from smallest to largest

Feature Goal Flow Features make up goals, and goals make up flows.

**Feature**

one thing the app lets a person do, named from its code. On BookStack: “Create a book”.

**Goal**

what a person wants to get done, using one or more features. On BookStack: “Update the permissions”, which rests on five routes.

**Flow**

how a person moves through the app, screen by screen, across one or more goals. On BookStack: “Delete an API token”, six screens from the home page to the delete page.

**The map**

all three for one app, and how they connect

**The review**

a person keeping, dropping or rewriting what featkpr drafted

## Where to look next

- [**What featkpr is, on one page** the home page](https://featkpr.com/)
- [**The problem it solves** why a map matters when coding agents do the work](https://featkpr.com/why#agents-h)
- [**What your team does with it** the questions, and how answers are kept](https://featkpr.com/#how-your-team-answers)
- [**The map, in the app** from one module down to one feature](https://featkpr.com/product/map#map-h)
- [**How features lead into each other** the flows, drawn as a tree](https://featkpr.com/why#runtime-h)
- [**What it found on a real app** BookStack, and what featkpr missed](https://featkpr.com/why#bookstack-h)
- [**Search every feature it named** the library](https://featkpr.com/library)
- [**The full BookStack report** for technical readers](https://featkpr.com/library/bookstack/reports/2026-09-26-bookstack-run#how-it-was-run)
- [**What is being built now** the roadmap](https://featkpr.com/roadmap)
- [**Ask for a private demo** half an hour, live](https://featkpr.com/demo#ask-h)

## See it on a real app

Half an hour with Tim, on BookStack, your questions first.

[Ask for a private demo](https://featkpr.com/demo)

---

The page this twin stands for: https://featkpr.com/start. Every page on this site has a `.md` twin, and answers `Accept: text/markdown`.