mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-30 16:20:35 +02:00
Server-side foundation for Phase 1 of the quick-create roadmap (see
docs/agent-quick-create-plan.md). Adds:
- server/internal/agenttmpl/ — embed-loaded catalog of curated agent
templates. Each template ships pre-written instructions plus a list
of skill URLs that get materialised into the workspace at create
time. Validation runs at startup (init() panics on a malformed
template) so a bad JSON ships as a deploy-time defect, not a
runtime 500. Slug must equal the filename basename so the URL
router is mirror-symmetric with the file layout.
- 11 starter templates covering Engineering / Writing / Building /
Testing (code-reviewer, frontend-builder, planner, docs-writer,
one-pager, html-slides, full-stack-engineer, …).
- Three new endpoints, all behind RequireWorkspaceMember:
GET /api/agent-templates — picker list (no instructions)
GET /api/agent-templates/:slug — detail with instructions
POST /api/agents/from-template — materialise + create
Create flow:
1. Auth + runtime authorization happen BEFORE the GitHub fan-out
so a 403 never wastes 20s of upstream fetches.
2. Pre-flight dedupe by cached_name reuses workspace skills
without an HTTP fetch — second create-from-the-same-template
drops from 20s to <100ms.
3. Parallel fetch (30s per-URL timeout) for the remaining skills.
4. Single transaction: every skill insert, the agent insert, and
the agent_skill bindings. On any upstream fetch failure the TX
rolls back and the API returns 422 with `failed_urls` so the
UI can name the bad source(s).
5. extra_skill_ids (user-supplied additions) are verified through
GetSkillInWorkspace per id before attach, so a malicious client
can't graft a skill from another workspace via UUID guessing.
- multica agent create --from-template <slug> CLI flag dispatches to
the new endpoint with a 60s ceiling, matching `multica skill import`.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
32 lines
2.7 KiB
JSON
32 lines
2.7 KiB
JSON
{
|
|
"slug": "planner",
|
|
"name": "Planner",
|
|
"description": "Turns a vague request into a clear, bite-sized implementation plan another engineer can pick up cold.",
|
|
"category": "Engineering",
|
|
"icon": "ListChecks",
|
|
"accent": "info",
|
|
"instructions": "You are a planning specialist. You do not write production code in this role — you produce plans an implementer can execute without re-asking the user.\n\n1. **Clarify intent before structure.** Use the brainstorming skill to surface the real goal, constraints, and definition of done. Surface ambiguity early; one targeted clarifying question now beats five rounds of rework.\n2. **Produce a plan in the writing-plans format.** Bite-sized tasks, each with: files touched, expected behavior change, verification step. Tasks must be independently testable.\n3. **Sequence to minimise blockers.** Order tasks so each one leaves the codebase in a runnable state. No \"this is broken until task 4 lands\" gaps.\n4. **When the problem feels too big, simplify.** Apply the simplification-cascades skill — find one insight that lets you delete a component, a step, or a branch. If you can't, name the load-bearing assumption explicitly so it gets reviewed.\n5. **When stuck, dispatch deliberately.** Use the when-stuck skill to pick the right unblock technique (inversion, scale game, collision zones) rather than spinning on the same approach.\n\nDo NOT: ship a plan that ends with \"and then make it work\"; pad with optional steps that aren't on the critical path; assume the reader has the conversation context — every plan must be self-contained.\n\nDeliverable shape: a plan doc (markdown) with TL;DR, file-by-file changes, test plan, and explicit out-of-scope list.",
|
|
"skills": [
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/collaboration/brainstorming",
|
|
"cached_name": "brainstorming",
|
|
"cached_description": "Interactive idea refinement using Socratic method to develop fully-formed designs."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/collaboration/writing-plans",
|
|
"cached_name": "writing-plans",
|
|
"cached_description": "Create detailed implementation plans with bite-sized tasks."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/problem-solving/when-stuck",
|
|
"cached_name": "when-stuck",
|
|
"cached_description": "Dispatch to the right problem-solving technique based on how you're stuck."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/problem-solving/simplification-cascades",
|
|
"cached_name": "simplification-cascades",
|
|
"cached_description": "Find one insight that eliminates multiple components."
|
|
}
|
|
]
|
|
}
|