Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By memorysaver
Run an autonomous per-feature development lifecycle: agentic planning, implementation, review, PR, merge, and feedback routing across git worktrees with minimal manual intervention.
Product-level opportunity and product framing. Use when starting a new product from scratch, revisiting product direction, or when the user says "new product idea", "validate this idea", "product framing", "what should we build", "revisit our assumptions". Walks through opportunity validation and produces a Context Document that feeds into /aep-map and /aep-design.
Decompose a product into system map, layered story graph, and agent topology. Use after /aep-envision, or when the user says "decompose", "story map", "system architecture", "break this down", "plan the stories", "agent topology". Produces the complete execution plan that the feature workflow operates on.
Classify feedback and update product context after shipping features. Use after /aep-wrap, after user testing, or when the user says "reflect", "what did we learn", "update the product context", "classify feedback", "replan". Closes the feedback loop by routing observations back to the right phase.
Generator/evaluator validation for any AEP artifact — product context, architecture, stories, code, or documents. Use after any generation phase (/aep-envision, /aep-map, /aep-design, /aep-build) or when the user says "validate", "verify", "check the design", "dry-run", "evaluate", "gen/eval", "generator evaluator". Spawns parallel agents: a Generator (dry-run the artifact), an Evaluator (check against reality), and optionally a Protocol Checker (verify downstream compatibility). Modifies only the artifact being validated — never implements code.
Full environment onboarding and first-hour orientation for Agentic Engineering Patterns (AEP). Use when setting up a new machine, joining the project, installing the plugin, or when the user says "get started", "onboard", "setup environment", "install prerequisites", "what is this plugin", "help me understand AEP", "I'm new to agentic engineering", "introduce me to this workflow", or wants to prepare their dev environment AND learn the mental model. Always use this first when a user mentions AEP, agentic-engineering-patterns, or this plugin for the first time.
Share bugs, ideas, or general feedback.
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.
A Claude Code plugin for building software products with AI agents — from raw idea to shipped MVP.
Traditional software development bottlenecks on human coding time. Process design optimizes "how to make people write code faster."
When agents can execute dozens of tasks in parallel, that bottleneck vanishes. A new one takes its place:
Agent execution capacity is near-infinite. Specification quality is not.
Vague specs don't slow down a human — they ask a colleague and adjust. Vague specs paralyze agents — they guess, diverge, and produce incompatible code across parallel sessions. The cost of ambiguity scales with parallelism.
This inverts the entire design logic:
Traditional: plan roughly → adjust as you go → ship
(optimizes for human coding speed)
Agentic: invest heavily in spec precision → parallel execution → ship
(optimizes for agent execution quality)
Every skill in this plugin serves that logic. The time you spend in /aep-envision and /aep-map pays back exponentially when agents build in parallel without asking questions.
AEP skills follow the open Agent Skills format, so any project — under
Claude Code, Codex, Cursor, OpenCode, and 70+ other agents —
can install them with the skills CLI. No clone, no copied scripts.
Prefer to delegate the install? Paste this to your coding agent — it covers the AEP skills, the
required OpenSpec CLI, the formatter fix, and wiring AEP into your AGENTS.md / CLAUDE.md:
Install the Agentic Engineering Patterns (AEP) skills into this project, pinned to the latest release.
1. Install the latest release for each agent this repo uses — find the newest tag at
https://github.com/memorysaver/agentic-engineering-patterns/releases/latest, then run once per agent:
npx skills add memorysaver/agentic-engineering-patterns@<latest-tag> -a claude-code --skill '*' -y
npx skills add memorysaver/agentic-engineering-patterns@<latest-tag> -a codex --skill '*' -y
This writes the skills under .claude/skills/ and/or .agents/skills/ plus a skills-lock.json manifest.
2. Commit the installed skill files together with skills-lock.json. The lockfile pins content
hashes, not the git tag, so the committed files are what durably lock that release — after that,
teammates and CI need no install step.
3. If this repo auto-formats Markdown/JSON on commit (Prettier, oxfmt, Biome, dprint, a
lefthook/husky hook): exclude .claude/skills/**, .agents/skills/**, and skills-lock.json from
the formatter, then make the install commit with --no-verify. Otherwise reformatting rewrites
the skill files and breaks the lockfile hashes.
4. Add a short section to AGENTS.md (and/or CLAUDE.md) so the workflow is discoverable:
## AEP Workflow
This project uses the Agentic Engineering Patterns (AEP) skills — a spec-driven, multi-agent
feature lifecycle in .claude/skills/ and/or .agents/skills/, pinned via skills-lock.json.
The skills are self-describing; start with `aep-onboard`. Upgrade by re-running
`npx skills add memorysaver/agentic-engineering-patterns@<newtag>` once per agent.
5. Verify with `npx skills list`. Restore from the lockfile later with `npx skills experimental_install`.
6. REQUIRED — install the OpenSpec CLI. AEP is a spec-driven workflow: its skills (/aep-scaffold,
/aep-dispatch, /aep-design, /aep-build, /aep-wrap) shell out to `openspec`, so it must be on PATH. Install it
globally (needs Node >= 20.19), then verify:
npm install -g @fission-ai/openspec@latest
openspec --version
AEP creates the per-project openspec/ artifacts itself — /aep-scaffold initializes them for a new
project, or run `openspec init` once in an existing repo.
Writing domain plugin - Content analysis, idea generation, and writing-kit workflow
Core workflow engine - Execute workflow-as-markdown definitions with validation-driven completion
Skills for setting up and aligning project-level agent layouts across Claude Code, Codex, and Pi Agent.
npx claudepluginhub memorysaver/agentic-engineering-patterns --plugin agentic-development-workflowDesign fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls
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.
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.
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.
Complete developer toolkit for Claude Code