Decompose pr-create into reusable Asana skills

Author: j0ntz

.cursor/skills/asana-plan/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: asana-plan
+description: Create an implementation plan from either an Asana task URL or ad-hoc text/file requirements, then wait for user confirmation before implementation.
+compatibility: Requires jq. ASANA_TOKEN for Asana context when task URLs are provided.
+metadata:
+  author: j0ntz
+---
+
+<goal>Produce a plan document via Cursor planning flow from Asana or text requirements, and hand off approved context to implementation skills.</goal>
+
+<rules description="Non-negotiable constraints.">
+<rule id="task-review-for-asana">If input is an Asana task URL, read and follow `~/.cursor/skills/task-review/SKILL.md` steps 1-3 before planning.</rule>
+<rule id="no-impl-before-confirm">Do not start implementation while in this skill. End by asking for confirmation.</rule>
+<rule id="create-plan-required">Use Cursor's plan tool to output the plan document to the normal planning location.</rule>
+</rules>
+
+<step id="1" name="Resolve input mode">
+Accept two input forms:
+
+1. **Asana URL mode**: Task URL is provided
+2. **Text/file mode**: Ad-hoc text requirement or file reference is provided
+
+If input is ambiguous, ask the user to clarify which mode applies.
+</step>
+
+<step id="2" name="Gather requirements">
+<sub-step name="Asana URL mode">
+Read `~/.cursor/skills/task-review/SKILL.md` and run its steps 1-3 to fetch and summarize task context.
+</sub-step>
+
+<sub-step name="Text/file mode">
+Read the provided description and any referenced file(s), then summarize scope, target areas, and assumptions.
+</sub-step>
+</step>
+
+<step id="3" name="Generate plan">
+Create a concise actionable implementation plan using Cursor's plan flow. Include:
+
+- Summary
+- Goal / Definition of Done
+- Likely relevant files
+- Findings so far
+- Numbered implementation steps
+- Constraints
+</step>
+
+<step id="4" name="Handoff and confirmation">
+Return:
+
+1. Plan file path
+2. Short execution summary (what will be changed)
+
+Then ask for confirmation before implementation:
+
+> Does this match your understanding? Any adjustments before I start?
+</step>
+
+<handoff-contract>
+`/im` consumes this output and starts only after user confirmation. `/im` should not re-run a second independent confirmation flow for the same plan.
+</handoff-contract>

.cursor/skills/asana-task-update/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: asana-task-update
+description: Update Asana tasks via one reusable workflow (attach PRs, assign/unassign, set status, and update task fields). Use when any skill needs to modify Asana task state.
+compatibility: Requires jq. ASANA_TOKEN for Asana API updates. ASANA_GITHUB_SECRET for PR attach operations.
+metadata:
+  author: j0ntz
+---
+
+<goal>Perform Asana task mutations through one shared command and one shared script, so all callers use the same field mappings and prompts.</goal>
+
+<rules description="Non-negotiable constraints.">
+<rule id="use-companion-script">Use `~/.cursor/skills/asana-task-update/scripts/asana-task-update.sh` for all Asana task mutations. Do not call raw Asana APIs directly from skills that can delegate here.</rule>
+<rule id="task-required">Every operation requires `--task <task_gid>`.</rule>
+<rule id="attach-requires-secret">`--attach-pr` requires `ASANA_GITHUB_SECRET`. Other operations require `ASANA_TOKEN`.</rule>
+<rule id="prompt-codes">If the script exits code 2 with `PROMPT_REVIEWER` or `PROMPT_IMPLEMENTOR`, ask the user and re-run with explicit `--reviewer` or `--implementor`.</rule>
+<rule id="script-timeouts">Asana updates can take time. Use `block_until_ms: 120000` for script calls.</rule>
+</rules>
+
+<usage>
+```bash
+# Attach only
+~/.cursor/skills/asana-task-update/scripts/asana-task-update.sh \
+  --task <task_gid> \
+  --attach-pr --pr-url <url> --pr-title "<title>" --pr-number <num>
+
+# Attach + assign reviewer + set review-needed status + estimate review hours
+~/.cursor/skills/asana-task-update/scripts/asana-task-update.sh \
+  --task <task_gid> \
+  --attach-pr --pr-url <url> --pr-title "<title>" --pr-number <num> \
+  --assign --set-status "Review Needed" --auto-est-review-hrs
+
+# Publish Needed -> Verification Needed (and unassign)
+~/.cursor/skills/asana-task-update/scripts/asana-task-update.sh \
+  --task <task_gid> \
+  --set-status "Verification Needed" --unassign
+```
+</usage>
+
+<step id="1" name="Build operation flags">
+Determine which updates are needed by the caller and build one command with all flags:
+
+- `--attach-pr --pr-url --pr-title --pr-number`
+- `--assign` or `--assign <user_gid>`
+- `--unassign`
+- `--set-status "Review Needed|Publish Needed|Verification Needed"`
+- `--set-reviewer <user_gid>`
+- `--set-implementor <user_gid>`
+- `--set-priority <enum_gid>`
+- `--set-planned <enum_gid>`
+- `--auto-est-review-hrs`
+</step>
+
+<step id="2" name="Run update script">
+Run `asana-task-update.sh` with the built flags. Prefer one call with combined operations over multiple calls.
+</step>
+
+<step id="3" name="Handle prompts">
+If exit code is 2:
+
+- `PROMPT_REVIEWER`: ask who to assign, then re-run with `--reviewer <gid>` and `--assign`
+- `PROMPT_IMPLEMENTOR`: ask who to set as implementor, then re-run with `--implementor <gid>`
+</step>
+
+<step id="4" name="Report result">
+Summarize one line per action from script output (attach result, assignment, status change, field updates).
+</step>
+
+<team-roster description="Asana user GIDs. Use numbered lists when prompting users.">
+1. Jon Tzeng — `1200972350160586`
+2. William Swanson — `10128869002320`
+3. Paul Puey — `9976421903322`
+4. Sam Holmes — `1198904591136142`
+5. Matthew Piche — `522823585857811`
+</team-roster>
+
+<exit-codes>
+- `0`: success
+- `1`: error
+- `2`: needs user input (`PROMPT_REVIEWER`, `PROMPT_IMPLEMENTOR`)
+</exit-codes>