doc2featurelisted

# Document-to-Feature Triage Convert prose documents (interview responses, audit narratives, analysis reports, handoff notes) into actionable `.aidd/features/` remediation entries by extracting claims, verifying each against the live codebase, and generating precise, verifiable feature.json specs. ## Usage ``` doc2feature <document-path-or-directory> [app] ``` - `<document-path-or-directory>`: Path to the prose document to process (markdown, text, or similar), **or** a directory of prose documents. When a directory is given (e.g. an interview's `.aidd/responses/`), process every `*.md` inside it as one combined claim corpus — read them all, extract claims across the whole set, and deduplicate claims that recur between files. A pure index file (a table of links with no prose answers, such as `.aidd/responses.md`) is not a source document; skip it and read the files it links instead. - `[app]`: Optional. If omitted, infer it from a document/directory path under `<applications-root>/<app-name>/.aidd/responses/`. If inference fails, return a usage error with the discovered candidate paths. ## Definitions - **Claim**: A statement in the document that asserts a specific deficiency, gap, vulnerability, placeholder, incomplete implementation, missing enforcement, or incorrect behavior exists in the codebase, with enough specificity to locate and verify - **Verification**: Reading the actual code referenced by a claim to confirm or refute its accuracy against the c