aep

Plugin aep from marketplace b10x in beyond10x/agentplugins. Commands read from the repo's manifest — yesterday.

Skills (11)

• decompose

  Decompose one epic into draft stories for the plan-critic panel; /aep:decompose <epic-id> or when asked to decompose an epic. Hands off to aep:planning.

• diagnosing

  Diagnose a reproducible bug or performance regression; a red-capable feedback loop first, then ranked falsifiable hypotheses, one-variable probes, a regression test, evidence in the AEP store. Use for diagnose, debug, "why is this failing", "this is slow", or broken, throwing, flaky or slower code.

• drive

  Start one governed AEP run over a single story; /aep:drive <story-id> or when asked to drive a story. Hands off to aep:implementing in drive mode.

• implementing

  Implement accepted AEP stories. Wave mode proposes the next wave of the `aep plan artifact waves` plan and stops for approval, then runs one implementor per story in its own worktree, adversary review, merges what is green, files pre-existing findings as backlog drafts. Drive mode hands one story to

• init

  Set up AEP (governed planning in a repository-local store, delivery in reviewed waves); make sure the `aep` CLI is installed and take the first step. Use when asked what AEP is, to adopt, set up or install it, or when an AEP skill reports `aep` missing. Installs CLIs only after the user confirms.

• investigating

  Investigate a production incident, an outage or a running system from citable evidence; state captured before remediation, a sourced UTC timeline, a healthy-peer comparison, every claim labelled verified or inferred. Use for investigate, "what happened", "when did this start", "is it still happening

• migrating

  Migrate legacy work tracking (story trees, TODO.md, plan and issue documents) into the AEP planning store without deleting or rewriting the sources. Use when asked to migrate, import or convert a backlog into AEP, when adopting AEP where work is already written down, or when a legacy backlog sits un

• planning

  Plan work in the governed AEP artifact store; create, relate, move and validate epics, stories, tasks and initiatives with the `aep` CLI. Use for planning, a backlog, epic, story or task, breaking down work, an artifact's status ("move this to active", "why can't this be implemented?"), adopting AEP

• review-plan

  Audit the AEP planning store for what `aep plan artifact validate` cannot see; /aep:review-plan or when asked to review the plan. Read-only, proposes moves and makes none. Hands off to aep:planning.

• upgrade

  Check whether the AEP plugin and the `aep` CLI are current and upgrade them on the user's confirmation. Use when asked whether AEP is up to date or to update it, when a `b10x:` session-start line names `aep`, or when `aep` behaves differently from an AEP skill or names the store's `aep.project` vers

• wave

  Propose the next wave of the AEP wave plan and stop for approval; /aep:wave or when asked to propose or start the next wave. Hands off to aep:implementing in wave mode.

Subagents (11)

• adversary

  Try to break a change that already passes its tests (edge cases, property violations, contract drift, a mutant the suite misses). Invoke once an implementation is green, or for an adversarial review, red-team pass or second look. Writes failing tests and returns findings; never edits the implementat

• decomposer

  Decompose one epic (e.g. `epic:passkey-login`) into draft stories that jointly cover it, when asked to break down, split or decompose it. Creates draft stories only; moves no artifact and edits none it did not create.

• implementor

  Implement one task or story id; the failing test first, then the smallest change that passes. Writes code and tests only, reports the suite's own output, never touches the planning store.

• plan-critic-acceptance

  Plan critic for a freshly drafted set; can every artifact be checked, with one acceptance statement naming an observable outcome and its state transition. Read-only, returns `approve` or `needs-revision` with cited findings.

• plan-critic-design

  Plan critic for a freshly drafted set; coupling between items, cycles in their edges, two items owning one surface. Read-only, returns `approve` or `needs-revision` with cited findings.

• plan-critic-parallel-safety

  Plan critic for a freshly drafted set; can it be worked in parallel, which items share a file and whether the plan says so, which name no surface (unassessed, not safe). Read-only, returns `approve` or `needs-revision` with cited findings.

• plan-critic-scope

  Plan critic for a freshly drafted set; is every outcome its parent promises claimed, and is nothing drafted the parent did not ask for or excluded. Read-only, returns `approve` or `needs-revision` with cited findings.

• plan-reviewer

  Read-only semantic audit of the planning store for what `aep plan artifact validate` cannot see (stale or drifted artifacts), when asked to review or audit the plan or before planning. Proposes moves, performs none.

• reverse-engineer

  Draft the first plan for an existing repository whose planning store is missing or covers none of it, through `aep plan reverse scan`, each draft citing its source. Invoke to adopt, bootstrap or reverse-engineer a backlog. Creates drafts only.

• security-reviewer

  Verify a change's safety and correctness invariants (boundaries, guards, a consumer's contract, an uncovered case). Invoke once an implementation is green, or for a security review, source review or independent second look. Writes failing conformance tests for unenforced invariants and returns findi

• story-scoper

  Work out where one story lands (crate, directory, files, symbols) and return its Scope section. One agent per story id, to scope, size or annotate stories or before selecting a wave. Read-only, so many run at once.

Similar plugins