aep-design
Designs a feature interactively on the integration branch into a reviewed OpenSpec proposal. Use for "design a feature" or "explore and propose".
How do I install this agent skill?
npx skills add https://github.com/memorysaver/agentic-engineering-patterns --skill aep-designIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates interactive feature design by coordinating between the user and various OpenSpec-related sub-skills. It uses standard development tools like git and GitHub/GitLab CLIs. While the workflow is structurally sound, it possesses an inherent indirect prompt injection surface because it ingests and processes user-supplied ideas and existing codebase content to generate design specifications.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Design
Interactive feature design on the integration branch ($BASE — resolve per /aep-git-ref "Resolving $BASE"). Explore the problem, propose a solution, review the design, and commit artifacts — all in conversation with the user.
Where this fits:
/aep-onboard → /aep-scaffold → [ /aep-design → /aep-launch → /aep-build → /aep-wrap ]
▲ you are here
Session: Main session, interactive with user Input: Feature idea or user request (optionally informed by product context) Output: OpenSpec change committed to the integration branch (proposal, design, specs, tasks)
Operating Mode
Auto-detect at startup:
ls product-context.yaml 2>/dev/null
- Standalone (no
product-context.yaml) — the feature lifecycle runs independently; proceed to Prerequisites. - Product-cycle (has
product-context.yaml) — the feature is a story in/aep-envision→/aep-map→/aep-dispatch→/aep-design. Read references/modes.md for how a dispatched story's context (acceptance criteria, interface obligations, existing change) loads before the phases.
Prerequisites
Two one-line checks — /aep-onboard installs missing tools, /aep-scaffold installs missing OpenSpec skills:
which git openspec >/dev/null 2>&1 && { which gh >/dev/null 2>&1 || which glab >/dev/null 2>&1; } || echo "MISSING cli tool → run /aep-onboard"
ls .claude/skills/openspec-{explore,propose,apply-change,archive-change}/SKILL.md >/dev/null 2>&1 || echo "MISSING openspec skill → run /aep-scaffold"
Workflow Mode Selection
Pick a workflow mode — full or light — before designing. It governs Phase 3 below and carries through to /aep-launch and /aep-build. Read references/workflow-modes.md for the two modes, the selection criteria, and how the choice is recorded so launch and build honor it.
Phase 1: OpenSpec Explore
/opsx:explore
Clarify requirements and scope with the user, investigate the codebase for relevant patterns, identify risks and unknowns, and create a docs/ architecture note if the feature warrants it.
Postcondition: requirements, scope, and risks are captured in the change directory (openspec/changes/<change-name>/).
Phase 2: OpenSpec Propose
/opsx:propose
Generates the full OpenSpec change: proposal.md (what/why), design.md (how, key decisions, risks), specs/**/*.md (requirements and scenarios), tasks.md (implementation checklist). When a story was dispatched, the change already exists — /opsx:propose refines it.
Postcondition: openspec/changes/<change-name>/proposal.md exists (alongside design.md, specs/, tasks.md).
Phase 3: Design Review
Review scope — architecture, interfaces, task decomposition — from non-functional angles:
- Security — auth gaps, injection surfaces, data exposure?
- Performance — N+1 queries, large payloads, blocking operations?
- Existing patterns — does it follow codebase conventions?
- Edge cases — concurrency, race conditions, failure modes?
Update the OpenSpec change files directly if adjustments are needed.
Light mode: skip Phase 3 entirely.
Postcondition: the user has approved the design, recorded in proposal.md (an approval note or checked box).
Commit to the Integration Branch
Commit the change directory and any architecture docs to $BASE as a control-plane commit — per /aep-git-ref "Control-Plane Commits" (resolve $BASE per /aep-git-ref "Resolving $BASE"). Stage explicitly with git add openspec/changes/<change-name>/ docs/ and message feat: add <change-name> architecture doc and OpenSpec change. This ensures the workspace has all artifacts when it is created from $BASE.
Postcondition: the change directory is committed and pushed to $BASE.
Next Step
Design is complete. Proceed to /aep-launch, which spawns an autonomous workspace session to implement the feature.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/memorysaver/agentic-engineering-patterns/aep-design">View aep-design on skillZs</a>