Meeting tasks

<!-- Generated from skills-src/meeting-tasks/SKILL.md — edit the source and run 'make gen-plugins'. -->

Meeting notes → Jira tasks with atl

Parse the notes → present the extracted items → get approval → create. Never create tickets before the user confirms the list. Command details live in the jira and confluence skills.

Preflight: atl must be installed and configured. If command -v atl fails or a command exits 7 ("not configured"), run /atl:setup and stop.

Workflow

1. Get the notes

Pasted text as-is, or use a guarded Confluence read:

<!-- atl:read-only-shell -->

export ATL_READ_ONLY=1
atl conf search --cql 'title ~ "<meeting title>" AND type = page' --limit 5 # when id is unknown
atl conf page outline <selected-id>
atl conf page sections <selected-id> \
  --heading '<actions heading>' --heading '<decisions heading>' \
  --max-bytes 65536 --expected-version <outline-version>

Use the exact selected id after search. A positive match may be selected early, but before claiming that no page exists, follow next_cursor until complete:true or narrow the query. Use the outline/sections path only when dedicated headings cover the notes needed for action extraction; otherwise read the complete page once with atl conf page view <selected-id> -o text. Never omit unstructured discussion merely to save context.

2. Extract action items

Signals: explicit markers ("AI:", "TODO", "Action:", checkboxes, "@name"), assignment verbs ("X will…", "X to…", "ask X to…"), and decisions that imply work ("agreed to migrate…"). Capture per item: the action as a verb phrase, the assignee as written, a due date if stated, and one sentence of surrounding context.

Skip pure decisions with no follow-up work and vague intentions ("we should think about…") — but list what you skipped, so the user can promote an item back.

3. Resolve assignees (Server/DC uses usernames)

<!-- atl:read-only-shell -->

export ATL_READ_ONLY=1
set -o pipefail
atl jira user search 'Alex Doe' --limit 10 |
  jq -c '{users:[.users[]|{name,key,displayName,active}]}'

Ambiguous or missing match → leave the task unassigned and flag it. Never guess between two people. This lookup is a bounded candidate surface without a completeness envelope, so an empty result does not prove that no user exists.

4. Present for approval

A table: # / summary / assignee (or ⚠ unresolved) / due date / source line. Ask for the target project key if unknown. Before presenting fields, qualify the issue type and create screen once for the whole batch:

<!-- atl:read-only-shell -->

export ATL_READ_ONLY=1
atl jira issue types --project KEY
atl jira issue create-check --project KEY --type '<exact returned type>'

Require complete metadata and reuse it for every item; do not repeat schema discovery per task. Wait for confirmation or edits.

5. Create tasks — sequentially

atl jira issue create preview --project KEY --type '<exact returned type>' \
  --summary '<verb-first action>' --from-md item.md \
  --field 'assignee={"name":"<username>"}' --field duedate=<YYYY-MM-DD>
env -u ATL_READ_ONLY atl jira issue create --project KEY --type '<exact returned type>' \
  --summary '<verb-first action>' --from-md item.md \
  --field 'assignee={"name":"<username>"}' --field duedate=<YYYY-MM-DD> \
  --apply --expected-proposal-hash '<reviewed hash>'

Description: Context (meeting name + date + the source lines) / What to do / link to the notes page if there is one. A mid-run failure → stop, report the keys created so far, ask how to proceed (atl never retries POSTs — do not blind-retry either).

6. Summarize and backlink

List created keys grouped by assignee. Offer to leave a "created tasks" comment on the source Confluence page. Put the exact body in a local CSF file, preview its complete baseline-bound proposal, and apply that same file once with the reviewed hash:

ATL_READ_ONLY=1 atl conf comment preview --id <pageId> --from-file follow-ups.csf
env -u ATL_READ_ONLY atl conf comment add --id <pageId> --from-file follow-ups.csf \
  --apply --expected-proposal-hash <reviewed-hash>

Only the second command writes, and only with explicit approval. Never replay outcome_unknown; it may already have created the comment.

Pitfalls

Symptom	Cause / fix
assignee rejected	must be the DC username from user search, not a display name or email
duedate rejected	the field may be off-screen for that project — drop it and note the date in the description
exit 8 on --from-md	unconvertible markdown block — the error names it; simplify