add-issue

Load the project config (contract in .darkflow.d/claude.md → Project config). Uses: language.

If $ARGUMENTS contains text (e.g. /darkflow:add-issue fix login button on mobile), use that text as the title — do not ask for a title again.

Walk through only the missing fields conversationally — skip any field already clear from the title:

1. What is it? (if not already clear) — bug, feature, or improvement? (just for your own framing — there's no separate type field)

2. Title (if not provided in $ARGUMENTS) — short action-oriented ("Fix X", "Add Y")

3. Priority:

   • critical — breaks revenue or a key feature right now
   • high — this week
   • medium — this month
   • low — someday / nice-to-have (allowed for manual tasks; scheduled routines never auto-create low)

4. Description — "Briefly describe the problem and what done looks like." Use the answer to fill the body template from docs/tasks.md → Task body — the template: a ## Problem paragraph, a ## Plan of 2–5 checkbox steps, and 1–3 ## Acceptance criteria — each one naming the command, report or URL that decides it. Do not ask the user for the plan: draft it yourself from the description and the code, and show it in the confirmation. Write the steps to be as independent as possible — each one lands on its own, leaves the project working, and could be done in a separate run; never make an early step depend on a later one, and merge two steps that only make sense together. If the work plainly does not fit one run (a migration, a refactor across many call sites), title the section ## Plan (multi-run) instead — fix-issues then takes as many steps as fit per tick and closes the task once the last one lands. Default to the plain ## Plan.

5. Timing (only if the user mentioned a date/"not before" constraint) — add --after <ISO date> to the create command so fix-issues won't pick the task up before that moment. Don't ask about this proactively.

Then construct and run:

~/.darkflow/df task create \
  --title "<title>" \
  --priority <p> --source manual --status approved \
  --body "$(cat <<'EOF'
## Problem

<description>

## Plan

- [ ] 1. <first concrete step — the file to touch, the change to make>
- [ ] 2. <second step>

## Acceptance criteria

- [ ] <criterion 1 — with the command / report / URL that decides it>
- [ ] <criterion 2 if needed>
EOF
)"

Important rules:

• Language for all conversation and task text: the language value from .darkflow.d/state/config.json (default: English)
• Always use --status approved — the user already decided to do it
• After creating, show the task number the command prints. The fix-issues routine will pick it up automatically.