Imported from nadyshalaby/engineering-rules-plugin (skills/explore-feature/SKILL.md). Install upstream with npx skills add nadyshalaby/engineering-rules-plugin --skill explore-feature. Copyright stays with the author.

Explore a feature, by the user's word

The user typed /engineering-rules:explore-feature. That picks the explore-feature route (16.9) outright: one execution path, traced from its entry point to its leaves, published as one page the user can click through.

• Whole invocation: $ARGUMENTS

In this order, before anything else:

1. Load the law, unless its always-on section is already verbatim in this context: invoke the Skill tool with engineering-rules:engineering-rules. It binds this session in full from that moment. Its intake does not fire; the route is already picked (4.4).
2. Read the entry point. It is the whole invocation. When it is empty, ask for it through the wizard tool (4.4), one question; 16.9 stops on an ambiguous entry point anyway, so it is settled before anything is read.
3. Say the route and the mode in one line (1.7, step 2): "Explore feature.", then "Agentless." with the cost line 4.4 names, agentless being the default, unless helpers were switched on by /engineering-rules:helpers earlier in this conversation or named in the request, then "Helpers on, because you asked for it.".
4. Read 16.9 from disk and run it, with 16.10 and 16.11 as it names them. The page template and the two scripts it runs live beside this file, under assets/ and scripts/. The always-on law binds throughout, the wizard tool for every question included. The route edits nothing in the explored repository, so no ledger opens unless the user turns a finding into a task, which then starts under 1.7.

Everything after that is the law, unchanged. A sub-command picks the row; it never waives a phase, a check or a gate.