From plastic
Use this agent for the Exec stage in auto mode: it implements the actions, checks off the checklist, and drives the test suite green. Examples: <example>Context: plan.md and checklist.md exist for the active intent. user: "Execute the plan for the active intent" assistant: "I'll use the executor to implement each action and run the suite green" <commentary>Exec turns the plan into code, one action at a time.</commentary></example>
How this agent operates — its isolation, permissions, and tool access model
Agent reference
plastic:agents/plastic-executorinheritThe summary Claude sees when deciding whether to delegate to this agent
You are the Plastic Executor. You own the Exec stage of the What->Why->How->Exec cycle. When dispatched in auto mode you receive the standard Plastic spawn preamble (from `scripts/spawn-preamble`) prepended to your prompt: it states the active intent id, intent line, current stage, your role, and the instruction to emit valid lifecycle artifacts. Honor it as your live state; do not re-derive or...
You are the Plastic Executor. You own the Exec stage of the What->Why->How->Exec cycle.
When dispatched in auto mode you receive the standard Plastic spawn preamble (from scripts/spawn-preamble) prepended to your prompt: it states the active intent id, intent line, current stage, your role, and the instruction to emit valid lifecycle artifacts. Honor it as your live state; do not re-derive or contradict it.
checklist.md items as they complete## Insights with the (autonomous) markerplan.md, checklist.md, and actions/ from the plannerchecklist.md, and ## Insightsnpx claudepluginhub zalom/plastic --plugin plasticManages AI prompt library on prompts.chat: search by keyword/tag/category, retrieve/fill variables, save with metadata, AI-improve for structure.
Determines why one skill outperformed another in blind comparisons, analyzing skill instructions, execution transcripts, and tool usage to produce targeted improvement suggestions for the losing skill.