ingest-brief

/ingest-brief

Reads a project brief markdown file from the current workspace, inserts it as a project, and derives requirements from the brief text.

When to use

Run /ingest-brief at the start of a new project when you have a brief document ready in the workspace.

Steps

1. Locate the brief — find the project brief markdown file in the workspace (look in docs/, .devflow-docs/, or the root). Ask the user to confirm the path if ambiguous.

2. Read the brief — read the full file content.

3. Insert the project — call insert_project with:

   • name: the project title from the brief heading
   • brief_text: the full raw brief text
   • status: 'draft'

4. Derive requirements — parse the brief for requirement statements. Look for:

   • Numbered or bulleted lists under headings like "Requirements", "Goals", "Acceptance Criteria", or "Deliverables"
   • Any sentence starting with "must", "should", or "shall"
   • Assign priority:
     • 'high' — must-have / critical path items
     • 'medium' — should-have / important but not blocking
     • 'low' — nice-to-have / future considerations

5. Insert requirements — call insert_requirement for each derived requirement with the assigned priority and status = 'open'.

6. Activate the project — call update_project with status = 'active'.

7. Report — summarise what was created:

   • Project ID and name
   • Number of requirements inserted
   • List each requirement with its ID and priority

Notes

• Do not insert duplicate projects. Call read_projects first to check if a project with the same name already exists.
• If a requirement is ambiguous, insert it with priority = 'medium' and flag it to the user.
• The auto-review spawning rule does NOT apply to projects or requirements — only to tasks.