itqanlisted

The full software-engineering lifecycle as one suite — DISCOVER, DEFINE, PLAN, BUILD, VERIFY, REVIEW, SHIP — with approval gates before code, test-first builds, evidence before "done", and resumable multi-session work. Routes to 12 sub-skills covering any stack, plus feature discovery, security audit, UI/UX craft, and learning roadmaps.
saleh-alhaddad/itqan-engineering · ★ 9 · Testing & QA · score 79

Install: claude install-skill saleh-alhaddad/itqan-engineering

# itqan — engineering skills suite router This repository is a **suite of 12 skills** sharing one backbone. When installed as a single skill (e.g. via `npx skills add`), this file is your map; everything referenced below ships inside this folder. **This suite is invoked explicitly — it never fires on its own.** The user names it; nothing here triggers from a matched description or keyword. `engineer` is the entry point for lifecycle work and routes to the phases itself, but every sub-skill is also a valid door in and bootstraps its own workspace (§1). If you are reading this file, you have been invoked: route and proceed. ## How to work 1. **Read [CONVENTIONS.md](CONVENTIONS.md) first** — the shared rules every sub-skill depends on (§1 workspace · §2 phase ledger · §5 resume sweep · §6 role dial · §7 gates · §8 multi-agent · §12 commit policy · §14 grounding · §15–17 session/big-change/freshness · §18 closing output · §19 data-driven decisions · §20 filesystem access & integrity). 2. **Route the task to the right sub-skill** and follow its `SKILL.md` exactly: | The user wants… | Follow | |---|---| | Something built/implemented/shipped end-to-end, or to "continue" prior work | [skills/engineer/SKILL.md](skills/engineer/SKILL.md) — the orchestrator | | Feature ideas / "what should we build next" | [skills/discover/SKILL.md](skills/discover/SKILL.md) | | A spec/PRD, or schema / data-model / API-contract design | [skills/define/SKILL.md](skills/define/SKILL.md) | |