itqan

Show what actually helps in this project - which workflows, agents and skills (from any plugin) were used, what the guard stopped, how many corrections were captured, and whether each approved rule is working or keeps being broken. Use when the user asks "is this helping", "what do I use", "which skills are useless", "insights", or "stats".

Review the project rules itqan learned from the user's repeated corrections and let the user approve, reword or reject each one. Approved rules are written to .itqan/rules.md and loaded every session. Use when the user says "learn", "what have you learned", "rules", "stop making that mistake", or when the session note says proposals are waiting.

Plan a change before writing code - acceptance criteria, the existing code it plugs into, tests to write first, ordered steps, risks. Produces a plan for approval and does not edit code. Use when the user says "plan", "how should we build", "design this feature", or before a change touching several files.

Make the proof that a change is done and save it as JSON - itqan runs the project's own tests, lint and build checks itself, and records the review verdict and the requirement checklist as reported. Use when the work is finished, after /itqan:ship, or when the user says "proof", "prove it", "show me it works", "أثبت", "وريني الدليل". mizan shows the latest proof in its pane.

Review code changes for real defects and security issues with specialist reviewers, verify every serious finding against the code, and report a ranked verdict. Works on uncommitted changes, the current branch, or a pull request. Use when the user says "review", "check my changes", "is this ready", or before merging.

Build a change end to end with quality gates - branch check, plan approval, failing tests first, minimal implementation until green, full verification, specialist review, then a commit proposal. Use when the user says "ship", "implement this properly", "build this feature", or "fix this bug with tests".