Menü
Architecture plan — tech decisions from an approved spec, before code
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Multi-slide bilingual brand carousels — Claude writes the deck, kun renders Anthropic-styled slides at exact platform sizes, a human approves, channels receive
Draft, stage, and publish brand social posts — Claude drafts, /higgs renders, a human approves, Hermes relays
Convert a file or URL to Markdown via MarkItDown (PDF, Office, images, audio, web)
Full pipeline — idea to production (chains every stage)
Autonomous block QA — detect, adversarially verify, fix safe tiers, hand the residual to a human
Technical spec — data model, file plan, refined acceptance criteria
Basierend auf der SOC-Berufsklassifikation
| name | plan |
| description | Architecture plan — tech decisions from an approved spec, before code |
| when_to_use | Use when turning a human-approved spec into an implementation plan — pattern choices, architecture decisions, mirror target, tradeoffs, and risks appended to the feature's GitHub issue — the pipeline Plan stage between /spec and /schema (NOT Claude Code plan mode). Triggers on: plan the architecture, architecture plan for the approved spec, pipeline Plan stage. |
| argument-hint | <feature>|#N [product] |
Turn an approved spec into an implementation plan: the architecture decisions, the pattern choices, and the risks — the how behind the spec's what. Sits between /spec (human-approved) and /schema. Resumable; skippable for trivial work.
/plan #42 — plan from issue number/plan billing — plan from feature name (finds the issue)/plan billing hogwarts — product-scopedgh issue view <N> --repo <repo> --comments
Require a ## Technical Spec comment AND human approval (the /spec checkpoint). If the spec is missing or unapproved, stop and route back to /spec. Extract: data model sketch, file plan, acceptance criteria.
Identify the closest existing feature to mirror (the spec usually names one). Read its content.tsx / actions.ts / form.tsx to lock the conventions this feature will follow. Note the canonical pattern cards that apply (.claude/patterns/cards/) and the domain rules (.claude/rules/<domain>/).
Delegate the architecture judgment to tech-lead (and the user-level architecture agent). Produce, using .claude/templates/plan.md as the shape:
'use cache' where it applies), auth + tenant-isolation placementgh issue comment <N> --repo <repo> --body "<plan>"
Header the comment ## Implementation Plan and end with *Generated by plan stage. Ready for task breakdown.*.
Plan comment exists on the issue with: pattern choices, architecture decisions, mirror target, tradeoffs, risks. Ready for /tasks.
Trivial features (a field add, a copy fix) don't need a plan — go straight to /schema or /code. The pipeline is a menu, not a mandate: /feature billing --from schema stays valid.