spec-mining-edho-ferdian

Run spec mining on the repository: it groups code into capabilities, reads entry points first, then expands one call-chain level to extract Requirements (WHEN/THEN) and Invariants. Each behavior is anchored to the exact file and method that enforces it.

A Requirement is triggered behavior with at least one WHEN/THEN scenario, such as returning an error when stock is insufficient. An Invariant is always true regardless of triggers, like a balance equaling the sum of transactions, and has no scenarios.

No, Salak is optional. The skill detects it at runtime and falls back to manifest and entry-point heuristics plus call-chain inference when absent. Salak-sourced dependency edges are labeled [Salak-verified]; inferred ones are labeled [inferred, unverified].

It cross-validates docstrings against actual callers before writing any Requirement, and records genuine ambiguity as explicit uncertainty comments instead of confident claims. A mandatory 5-gate reflection checks traceability, provenance, and labeling before handoff.

Expansion stops at the first of: an external system boundary, three consecutive files yielding no new behavior, or 15 total files read per capability. Unread files are recorded with reasons in a deferred metadata comment, never silently dropped.

It writes one Markdown file per capability to /project-memory/mined-specs/<capability>.md, creating only that subdirectory if missing. The format is tool-agnostic and optionally exportable to OpenSpec's openspec/specs layout.