user-request

To capture user requests verbatim, record the feature request without paraphrase to preserve original intent. This action creates an immutable, auditable record stored as an initial task, which then automatically seeds subsequent classification and research phases.

Tracking feature requests as an immutable record requires capturing verbatim input directly into a task management workflow. This unmodified capture acts as a single source of truth that feeds downstream analysis, classification, and decision-making tasks.

Verbatim capture seeds classification and research tasks by storing the unmodified user request and attaching classification labels as linked tasks. This mechanism automatically creates Phase 2 elicitation tasks assigned to an architect for downstream exploration.

You need an existing workflow to classify and research user requests because verbatim capture specifically serves as Phase 1 of an epoch workflow. It relies on this structured environment to trigger prerequisites and automatically generate subsequent Phase 2 tasks.

You can use task management beads for user request classification by attaching classification labels directly to the beads tasks. This links the unmodified verbatim capture with structured workflow phases, triggering subsequent analysis and Phase 2 prerequisites.