# Answer library maintenance

A reusable skill the "Clear security questionnaires without guessing" recipe pulls in. Add it once and every agent on the team can use it.

Grow and version the approved-answer library so every new questionnaire starts with more coverage than the last.

## Method
1. Store the library as one row per question pattern, not per questionnaire.
2. Give each row six fields: question pattern, approved answer text, evidence citation, version number, last-updated date, approver name.
3. When a questionnaire completes, collect every answer the human reviewer signed off on.
4. Add each signed-off answer as a new row, or a new version of an existing row if the wording changed.
5. Search the library by closest-match on question pattern before drafting any new answer.
6. Retire a superseded version by marking it inactive — never delete it, so past citations still resolve.

## Rules
- Only a human-approved answer enters the library; an agent-drafted-but-unreviewed answer never does.
- Every row carries an evidence citation — a policy doc, a control ID, or a prior signed answer.
- Version every edit; never overwrite a row in place.
- Categories that always need human review regardless of a library match: (set on first run, then stored in memory).

## Output
An updated answer-library sheet: new or versioned rows, each with question pattern, answer, citation, version, date, approver.