Document Workflow & Status System - KFB Feature Database

What this is

The lifecycle every document moves through -- Needed, Seeded, Draft, Active, Final, Restricted -- plus the seeded-item warning (so information mentioned in conversation but never saved doesn't get lost) and the plain-language command set for producing and committing documents.

install document-workflow-and-status

Optional: false · Depends on: none · Registry refs: [2.10, 5.15, 5.16]

The sections below are the install payload — the directives Claude reads and runs when this feature is installed. Shown here for transparency; a person browsing only needs "What this is" above.

Assess first

- Read `admin\AGENT_INSTRUCTIONS.md` for any existing status set or workflow commands and carry them forward.
- Note whether the Document Tracker System is installed -- statuses are recorded on tracker cards, but this workflow stands alone even without a tracker.

Ask, only if needed

Nothing to ask -- proceed directly to Write.

Write (payload written into admin\AGENT_INSTRUCTIONS.md)

Add this section to `admin\AGENT_INSTRUCTIONS.md`:

```
* DOCUMENT WORKFLOW & STATUS SYSTEM

Statuses: Needed -> Seeded -> Draft -> Active -> Final -> Restricted

| Status     | Meaning                                                    |
|------------|------------------------------------------------------------|
| Needed     | Identified, not started                                    |
| Seeded     | Info in conversation only -- NOT on the file system         |
| Draft      | File exists, in progress (_Draft in filename)              |
| Active     | Current working version                                    |
| Final      | Approved and complete                                      |
| Restricted | Exists but sensitive -- not surfaced in normal conversation.|
|            | Agent acknowledges existence but does not display content  |
|            | without explicit user instruction.                         |

SEEDED WARNING
If seeded items exist, remind before the conversation closes (and
periodically during long sessions):
"You have seeded content not committed yet: [list]. Want to commit any of
these before you go?"

STANDARD WORKFLOW
Session info -> "show me [code]" -> markdown in conversation
-> "commit to draft" -> versioned .md -> refine
-> "make the Word document" -> .docx
-> final review -> "commit to final" -> version updated
-> PDF only when ready to publish

WORKFLOW COMMANDS
| Say this               | Agent does                          |
|------------------------|-------------------------------------|
| "Show me [code]"       | Markdown in conversation            |
| "Commit to draft"      | Versioned .md file                  |
| "Make the Word doc"    | .docx produced                      |
| "Commit to final"      | Tracker updated, _Draft removed     |
| "Render the tracker"   | Card view in conversation           |
| "Update [code] to [X]" | Tracker item updated                |
| "Generate a handoff"   | Session transfer document           |
| "Run an audit"         | Full project health check           |

First time a user asks to produce a document: briefly walk through the
workflow (session -> markdown -> Word -> PDF). If they try to skip to PDF:
"Let's get this into Word first -- that's your editable master. PDF comes
after. Kevin backs me up on this one."
```

Confirm

Confirm: your document workflow and status system is installed -- statuses, the seeded-item warning, and the command set are in the agent instructions. Want to install another, or is that everything for now?