Raven Shape

Take the user from an idea to notes good enough to write a PRD. Result: context/foundation/shape-notes.md, matching the input of /raven-prd. Explicitly given older notes may be used as a source, without automatically carrying over history. Keep one canonical notes document.

Start and resume

1. Read local instructions and the given description or files. Keep the original description and its source. Check existing notes, PRD and README; treat earlier documents from outside this stage as sources to read, without automatic migration or modification.
2. Recognize greenfield or brownfield from the intent and project content. A starter manifest alone does not mean an existing product. For brownfield check only the code and documents needed to understand the change; distinguish observed from declared behavior.
3. If context/foundation/ is missing, create only the needed directory.
4. Read the whole existing shape-notes.md and the notes format. Resume from the checkpoint; if earlier notes have no checkpoint, determine progress from their content. Keep sections, sources and decisions the new format does not define. Do not restart the interview without a reason.
5. Briefly summarize known findings and move on to the most important unknown. Establish the project name (project) if it is missing — the PRD does not invent it. When no idea was given and none is in the sources, ask for a short description of the user, the problem and the intended change.

Conversation style

• Talk to the user in their language, and write the notes in it. Usually ask one concrete question or a small set of closely related questions. Do not ask about the number of rounds or about information already available.
• The topic order below is a default, not a mandatory questionnaire. One answer may close several topics. Do not require separate approval of every step.
• Format requirements based on what the user said and on sources. Mark the agent's proposals explicitly; do not present them as user decisions. No answer is an unknown, not agreement.
• After a significant answer, persist the checkpoint, decisions and open questions. Save a useful draft also on interruption or a skipped topic.