wicked-garden:archetype

To route prompts to workflow archetypes, tag your input with <wg archetype="X">. This triggers the corresponding archetype runner, which loads per-archetype playbooks and executes the phase shape defined in your configuration.

Prompt orchestration via work-shape archetypes is a routing mechanism that directs prompts to specialized runners. It applies per-archetype playbooks from reference files to execute defined workflow phases like triage, explore, specify, and ship.

You can invoke an archetype runner by using slash commands or responding to system reminders that resolve to the skill. Tagging your prompt with the appropriate archetype tag automatically routes the work to the correct runner.

Yes, archetype playbooks support incident response and migration tasks. The routing system covers nine archetypes including incident, migrate, build, review, decide, and ship, each loading specific phase shapes from reference files.

Yes, archetype routing requires configuration defined in .claude-plugin/archetypes.json and per-archetype playbooks stored in the refs/ directory. These files declare the phase shape and execution logic for each of the nine available archetypes.

The best way to automate prompt routing across workflow phases is to use the central archetype entry point. It identifies the target archetype from your prompt tags and orchestrates the declared phase shape, automating the entire execution flow.