| description | agent |
|---|---|
Parse context and create beads from it |
build |
Parse the current conversation or provided context and create beads issues from it.
If $ARGUMENTS is provided, treat it as context to parse (e.g., a list of tasks, requirements, or TODOs).
Steps:
-
Analyze the conversation or provided context for:
- Action items and tasks
- Bugs that need fixing
- Features to implement
- Technical debt to address
- TODOs mentioned in discussion
-
For each identified item, determine:
- Title (clear, concise description)
- Type (bug, feature, task, chore, epic)
- Priority (0=critical, 1=high, 2=medium, 3=low, 4=backlog)
- Dependencies (does this block or depend on other items?)
-
Check existing issues to avoid duplicates:
bd list --json -
Create issues for new items:
bd create "Title" -t <type> -p <priority> -d "Description" --json -
Set up dependencies between related issues:
bd dep add <child> <parent> -
For large features, consider creating an epic with child tasks.
-
Sync changes:
bd sync -
Report summary of all issues created with their IDs.