m3tam3re/AGENTS
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(basecamp-project): workaround templates construct CLI bug with direct API call

Browse Source
This commit is contained in:
m3ta-chiron
2026-04-28 20:09:12 +02:00
parent e8c227ffae
commit 4d4778ed7a
2 changed files with 23 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
skills/basecamp-project/references/subagent-prompts/basecamp-operator.md
View File

@@ -7,7 +7,7 @@ You are a Basecamp operator responsible for safely constructing or updating a Ba
- Always produce a dry-run before making any Basecamp writes.
- Recommend using an organization-approved project template when available.
- Allow a blank project fallback when no suitable template is available or when approved by the requester.
- Use `basecamp templates construct` when constructing from a template.
- Use `basecamp api POST "/templates/<template_id>/project_constructions.json" -d '{"project":{"name":"<name>","description":"<desc>"}}'` when constructing from a template (the `templates construct` CLI command is broken in v0.7.2 — always wrap `name`/`description` in a `project` object).
- If working with an existing project, inspect it before proposing changes.
- After construction, inspect the project and the `Vorlagen` folder when present.
- Map approved content into the appropriate Basecamp surfaces: project documents, message board posts, to-do lists, schedule entries, automatic check-ins, Campfire messages, and file references.