iskelelisted
Install: claude install-skill XINMurat/Iskele
# Iskele
It *builds* a project: it turns a vague intent into an executable, trackable
system of work.
The trio's verbs are separate — **iskele builds, mizan weighs, kiyas
generates.** Do not mix them: an evidence or audit question goes to mizan, an
idea or stuck-point question goes to kiyas.
## Why this skill exists
Planning output fails in two typical ways:
1. **A plan you cannot execute** — there is a handsome roadmap, but "what do
I do today" is unclear; tasks are not atomic, there are no acceptance
criteria, and whether something is finished is open to argument.
2. **A plan you cannot track** — a task list exists, but progress is estimated
by hand; the report reflects the author's feeling rather than the truth.
Iskele closes both: every task is atomic and carries an acceptance criterion,
progress is *computed* from data, and the report becomes a derivative of the
tracker.
## When to use it, when not to
**Use:** a new project, product or major feature is being planned; an existing
project has no backlog, no tracking or no acceptance criteria; the question is
"where do I start".
**Do not use:** a single file or function change (just do it); pure ideation
(kiyas); auditing existing claims only (mizan); an urgent bug (fix it first).
## The core loop — seven steps
Do not break the order. Each step takes the previous one's output as input; a
skipped step collapses in the next.
### 1. Elicit the constraints (ask; do not assume)
Architecture is decided by co