Onboard a target repository into the workflow conventions — docs/prd/, docs/adr/, and the AGENTS.md shim. Idempotent, a thin pointer at `lore attach --scaffold-workflow`. Use when setting up a repo to adopt the workflow skills.
Systematic root-cause debugging with a hard circuit breaker. Use when a bug resists fixing, a test keeps failing, a teammate is stuck after repeated fix attempts, or you catch yourself guessing at fixes instead of finding the cause.
After an epic merges, update a repo's Diátaxis documentation (tutorials, how-to, reference, explanation) to reflect the implemented state, then open a docs PR that auto-merges on green. NEVER touches docs/prd or docs/adr. Use after an epic lands and its user-facing docs need to catch up. Standalone and cross-repo aware.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
A relentless interview to sharpen a plan or design.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Fast path for one well-understood GitHub issue — read the issue and the code map, clarify only if needed, then TDD it on one branch to one PR with the ADR and docs gates applied. Use when the user points at a single clear issue and wants it implemented directly, not run through the whole epic chain.