ef

Plugin ef from marketplace ef-harness in micaelcf/ef-harness. Commands read from the repo's manifest — 4 days ago.

Skills (9)

• ef-adversarial-audit

  Stage 5 - adversarially audit delivered work against its requirements assuming a green test suite proves nothing, then verify that claimed fixes are real, then emit the code-verified contract document other repositories build against. Use after implementing a feature in a repo, after remediating aud

• ef-feature-docs

  Stage 2 - author a feature's documentation folder from closed grill decisions: grill-decisions to RFC to PRD to INDEX, with mandatory fields gated by asking rather than invented, stable requirement identifiers, and an amendment protocol that keeps the documents alive through implementation. Use afte

• ef-grilling

  Relentless one-question-at-a-time interview that converts an under-specified plan into closed decisions, each recorded with its evidence grade, preserved dissent, riskiest assumption and reopen condition. Runs at product altitude as Stage 1 of a feature, or at repo altitude as the decision step of a

• ef-implement

  Stage 4 - turn closed decisions and a written contract into checks with named proofs, then orchestrate the build in parallel slices and hand a whole feature to the audit. Use when discovery closed, the contract is written, or the user says implement this feature, build this ticket, extract a checkli

• ef-perspective-discovery

  Discover a feature from the current repository's perspective, after it was defined upstream at product altitude: verify the docs' code anchors, fan out read-only scouts, triage contradictions, grill the survivors, then write the contract. Use when handed a feature-docs folder (grill-decisions/RFC/PR

• ef-prototype

  Discover a brand-new UI before implementing it: generate 4-5 radically different variants of one screen in a single shareable HTML file, switchable from a floating bar, then pick one and let it govern the requirements and the contract. Use when a feature introduces a screen, page or component that i

• ef-readiness

  Make a repository's agent rulebook (AGENTS.md / CLAUDE.md) verifiable: vendor a deterministic checker, audit every rule and citation against the code, bootstrap a lean rulebook from what the code cannot say, and grow it from audit findings. Use when setting a repo up for agents, when asked to audit

• ef-shared

  Shared vocabulary for every ef-* stage: the A–D evidence grades and the five critical lenses (assumption-surfacing, pre-mortem, red-team, evidence-audit, second-order). Load when an ef-* skill tells you to grade a claim or apply a lens. Not a workflow on its own.

• ef-to-jira

  Turn any feature description into a small, product-level Jira issue set: settle project and language, size by semantic change, write a draft, and push through the host's own Jira tools only after explicit approval. Standalone and optional: no EF docs required, outside the five stages. Use when the u

Slash commands (9)

• /ef:audit

  Stage 5 - adversarial audit of delivered work against its requirements, verification that claimed fixes are real, then the code-verified contract doc

• /ef:feature-docs

  Stage 2 - author the feature folder (RFC, PRD, INDEX) from closed grill decisions

• /ef:grilling

  Relentless one-question-at-a-time interview that closes every open decision before implementation starts - Stage 1 of a feature at product altitude, or the decision stage of a repo discovery

• /ef:implement

  Stage 4 - extract checks with named proofs from the contract, then orchestrate the build in parallel slices

• /ef:perspective-discovery

  Stage 3 - discover a feature from THIS repo's perspective before implementing it - anchor check, scout fan-out, contradiction triage, then grill

• /ef:prototype

  Discover a brand-new UI before building it - 4-5 radically different variants in one shareable HTML file

• /ef:ready

  Make the repo's agent rulebook verifiable - vendor the checker, then audit, bootstrap, or grow AGENTS.md from audit findings

• /ef:spec-drift

  Stage 3 pre-check - verify every code anchor in a feature's docs still resolves in this repo

• /ef:to-jira

  Turn a feature into a small, product-level Jira issue set - draft first, push through the host's Jira tools only after explicit approval

Hooks (1)

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}"/hooks/claude-post-edit.mjs

Similar plugins