All authors
Claude Skills by micaelcf
github.com/micaelcf7 skills0 installs0 views
- Ef Adversarial AuditStage 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 audit findings, or when handing a feature to another repo.Votes: 0GitHub stars: 4
- Ef Feature DocsStage 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 after a product-altitude grilling has closed the decisions, or when the user says write the RFC, write the PRD, author the feature docs.Votes: 0GitHub stars: 4
- Ef GrillingRelentless 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 discovery. Use when the user says grill me, stress-test this plan, close the open decisions, or when a feature needs defining before anything is built. Do NOT use to write the RFC or PRD, or to im...Votes: 0GitHub stars: 4
- Ef ImplementStage 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 checklist, ef-implement. Do NOT use when nobody has decided what to build, or to design the work.Votes: 0GitHub stars: 4
- Ef Perspective DiscoveryDiscover 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/PRD) produced elsewhere, once per target repo, before implementing.Votes: 0GitHub stars: 4
- Ef PrototypeDiscover 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 is not a variation of anything the repo already has. Do NOT use for forms, tables, list-detail, settings panes, modals or any well-known pattern, and do NOT use to prototype logic or state models.Votes: 0GitHub stars: 4
- Ef SharedShared 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.Votes: 0GitHub stars: 4