Document todo subtask API usage in Basecamp skill

[bjoycerobo]

What

Document Basecamp todo subtask/checklist-step handling in skills/basecamp/SKILL.md:

• Todo subtasks are represented as Kanban::Step records even when parented to a normal Todo.
• Add raw API examples for creating, reading, editing, assigning, setting due dates, completing/reopening, and trashing todo subtasks.
• Note practical agent gotchas discovered during testing: preserve title when updating metadata, use assignee_ids instead of basecamp assign --step for todo-backed steps, and use recordings trash rather than DELETE to remove the subtask from the todo UI.

Why

The existing skill documents card steps, but todo-backed subtasks are not exposed through the normal todos commands and can be easy for agents to miss or handle incorrectly. This gives agents a verified workflow for managing these subtasks through the raw API until/if first-class CLI commands exist.

Testing

• Manually verified against a real Basecamp todo subtask:
  • Created and read todo subtasks through the card_tables/steps API.
  • Assigned a subtask and set due_on via raw step update with assignee_ids.
  • Confirmed basecamp assign --step returned Bad Request for a todo-backed step.
  • Trashed a subtask with basecamp recordings trash and confirmed it disappeared from the todo UI while direct reads returned status: "trashed".
• make check passes

---

Summary by cubic

Documents how to manage Basecamp to‑do subtasks (checklist steps) in skills/basecamp/SKILL.md via raw card_tables/steps APIs, with examples for create/read/update, assign/due dates, complete/reopen via /completions.json, and trash. Clarifies subtasks are Kanban::Step items discoverable via basecamp recordings --type Kanban::Step filtered by parent.id, confirms the creation path /card_tables/cards/<parent_todo_id>/steps.json, documents status fields (completed, completion, status: "trashed", inherits_status: false), lists GET routes that return not_found, and notes gotchas: include title on updates, prefer assignee_ids, and use --status trashed/--status archived when inspecting removed subtasks.

^{Written for commit 463a368. Summary will update on new commits.}

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds documentation to the Basecamp skill guide explaining how to work with Basecamp to-do subtasks (stored as Kanban::Step) via the raw API, including create/read/update/complete/trash workflows.

Changes:

• Documented where to-do subtasks live in Basecamp’s data model (Kanban::Step) and how to find/read them.
• Added raw API CLI examples for creating, updating (including assignment/due dates), completing/reopening, and trashing subtasks.
• Clarified status/fields differences for completed, open, and trashed subtasks, plus caveats about updates and basecamp assign.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.