wkc-research

• What it does: turns research material and the user's answers into the PRD at prd_file: what the product is for, who it serves, and which evidence supports that.
• When to use it: starting a product, or a change that shifts its goals, users, or scope. Re-run it when new research arrives. A small feature or fix that fits the current intent does not need it: do the work and update the PRD afterwards if something it says changed. Callers are people.
• Dependencies: prd_file from docs/dev-agents/config.md, falling back to docs/dev-agents/PRD.md when there is no config. The harness's own tools for reading files, documents, images, and URLs. No tracker.
• Input: free text: an idea, notes, file paths, or URLs. With nothing given, read the existing PRD and project context, then ask what changed, or, with no PRD, what problem the product solves.
• Output: the PRD file, plus a short report of what changed, what is still open, and whether the PRD is approved. wkc-architect reads an approved PRD next.

Writes only the PRD. Keep what the user wrote in it unless they ask to change it.

1. Read before asking