By zalom
Intent-driven state management for AI coding sessions. Neuroplasticity for your codebase.
Use this agent for the Why-stage exploration of an active intent in auto mode: it enriches context and records decisions before a spec is written. Examples: <example>Context: An intent has a What but a thin Why. user: "Explore the requirements for the active intent" assistant: "I'll use the brainstorming agent to enrich Context and record Decisions" <commentary>Why-stage exploration runs before the spec-specialist.</commentary></example>
Use this agent as the auto-mode orchestrator: it spins up the team, sequences the specialists, owns every gate, and runs the final review. Examples: <example>Context: User triggers auto on an active intent. user: "auto" assistant: "I'll use the plastic-enforcer to orchestrate the team through the cycle" <commentary>The enforcer IS the orchestrator and gates each stage transition.</commentary></example>
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>
Use this agent to research future intents autonomously. Picks up parked intents from INDEX.md, investigates them via web search and codebase analysis, and writes findings into the intent. Examples: <example>Context: There are future intents parked in the index. user: "Research my future intents" assistant: "I'll use the future-intent-researcher to pick up a parked intent and investigate it" <commentary>Agent autonomously researches a future intent and writes findings.</commentary></example>
Use this agent when completing or reviewing intents, reorganizing the index, or when the intent store needs maintenance. Examples: <example>Context: User has finished implementing a feature. user: "This intent is done, clean up the index" assistant: "I'll use the intent-curator agent to update the intent status and reorganize INDEX.md" <commentary>Intent lifecycle change triggers curator for index maintenance.</commentary></example> <example>Context: The intent store has grown and clusters need review. user: "Organize the intents" assistant: "I'll use the intent-curator to review clusters, flag orphans, and suggest connections" <commentary>Periodic maintenance of the Zettelkasten structure.</commentary></example>
Add an intent store to a project that is already registered in projects.yml but has no store on disk. Use when a project is registered but has no store, when you need to provision a store, or when doctor reports a missing project store (project_store_dir). Thin wrapper around provision-project-store plus an optional qmd register step.
Autonomous intent delivery — agent takes over How and Exec. Use when user says "auto", "take it from here", "deliver this", or when brainstorming-grill-me concludes and user confirms autonomous execution. Requires an active intent in INDEX.md.
Deep brainstorming that interviews the user relentlessly about a plan or design until reaching shared understanding. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Pair with plastic-brainstorming for quick ideation and use grill-me for thorough interrogation. If superpowers:brainstorming is installed it complements this skill, but it is not required.
Explore intent requirements and design before implementation. Produces spec.md in the active intent directory.
Use when the user says "continue", "resume", or "pick up where we left off", or when starting a new session. Continues work with the latest project context: lands on the right dashboard, then presents choices. Boot (health check, core context, version, statusline) is owned by the SessionStart hook, not this skill. Does not drive work autonomously (that is plastic-auto).
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Alpha software. Expect breaking changes between releases. Install:
npx @zalom/plastic@alpha --claude
Intent-driven idea development system for AI coding agents. Named after neuroplasticity: adaptive, malleable, dynamic, resilient.
Plastic thinks in intents, not tasks. An intent is a desire, something you want to accomplish, explore, or understand. Intents are atomic thoughts that get developed through two nested processes.
Coordinator loop (B→O→R): Brainstorm → Organize → Review. The human and agent explore ideas, structure them into intents, and validate the results. This loop runs continuously across sessions.
Intent lifecycle (W→W→H→E): Why → What → How → Execute. Each intent moves
from motivation through specification, planning, to delivery. Intents produce
artifacts: spec.md, plan.md, checklist.md, outcome.md.
Plastic is a thinking system, a blueprint for taking a desire from intent to delivery. It splits the work in two:
Determinism lives in the form of the work (section sets, ordering, schemas, naming, IDs, file layout), never in the brain's reasoning. The framework stays constant while the thinking varies. Run Plastic on Claude Code, Codex, Hermes, OpenClaw, or by hand on paper in Obsidian or Word, and the only thing that changes is the quality of thought. The proof is the paper test: if a person with no tooling and no AI can reproduce a correctly-shaped intent, the determinism is in the form, not the agent.
Deterministic by design, free by intent. The rigid part is rigid on purpose. It is what makes work portable, reviewable, and resumable across any agent. The free part is free on purpose. It is where the brain's creativity lives. Plastic draws the line between the two and holds it.
Harnesses are how it holds the line. Shared harnesses (conventions, templates, and directory structure) constrain humans and agents alike. Agent-extra harnesses (evals that check a skill's output, plus hooks and instructions that steer reasoning) give an agent the instincts a careful person already has: stop and save state, leave a note when the context runs out, never plan before specifying.
This is intent-driven delivery, a new shape for the software lifecycle in the age of agentic engineering. The unit of work is an intent, not a ticket, and every intent carries its own spec, plan, checklist, and outcome as it moves through Why, What, How, and Execute. What you get is agent-agnostic, auditable, and additive: a knowledge graph of why things were built, not just what.
Plastic requires Ruby (pre-installed on macOS/Linux) and Node.js 18+.
# Alpha (current, active development)
npx @zalom/plastic@alpha --claude
# Beta (when available, API-stable, bug hunting)
npx @zalom/plastic@beta --claude
# Stable (when available, general use)
npx @zalom/plastic --claude
Replace --claude with --codex for Codex CLI, --hermes for Hermes, or
--all for all supported agents.
Bun users can substitute bunx for npx (e.g. bunx @zalom/plastic@alpha --claude).
Bun is never required.
Skills install as flat, hyphen-namespaced personal skills (plastic-doctor,
plastic-auto, and so on). Invoke them with a hyphen. Plastic is not a Claude Code
plugin; re-running the installer auto-removes any legacy plugin registration.
From within your agent, say "update plastic" or run:
npx @zalom/plastic@alpha --claude
The plastic-update command shows available versions across all channels and
lets you choose which to install.
After installation, run /clear to load Plastic conventions, then:
/plastic-creating-intent to create your first intent/plastic-brainstorming to explore the design/plastic-writing-plans to create an implementation plan/plastic-executing-plan to deliver itOr say "auto" to let the agent handle the full lifecycle autonomously.
docs/architecture.md: system structure, the two
processes, the store layout, and the component map.docs/internals.md: how Plastic stays deterministic, the
determinism breakdown, and the harness system.npx claudepluginhub zalom/plastic --plugin plasticFeature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.