İskele — From a Vague Project Intent to an Executable Delivery Kit

A Claude skill that turns a vague project intent into a domain model, a phased roadmap with gates, an atomic backlog with acceptance criteria, quality gates, a tracker and a self-regenerating progress report. Bilingual TR/EN.

View the Project on GitHub XINMurat/Iskele

İskele

From a vague project intent to an executable delivery kit, packaged as a Claude skill. Belirsiz bir proje niyetinden koşulabilir bir teslim kitine — bir Claude skill’i olarak paketlenmiş.

Repository · Latest release · Mizan · Kıyas · ux-mizan · the family · aile


English

“I know roughly what I want to build” is not a plan, and neither is a task list someone wrote in one sitting. İskele turns the first into the second and then into something you can actually run against: a domain model, a phased roadmap whose phases have gates, an atomic backlog where every task carries an acceptance criterion, a Definition-of-Done, a tracker, and a progress report that regenerates itself from the tracker rather than from someone’s impression of how things are going.

Two properties it refuses to give up. Every task names its arbiter — who returns the verdict that the criterion was met — and a task whose only judge is the person who did the work stays self-reported, never silently promoted. And the progress report rewrites only its generated regions, so hand-written context survives regeneration.

A note on languages. The packaged skill body is English — like Mizan and Kıyas, for portability across hosts — and the Turkish originals of SKILL.md and the three references live in tr/: metodoloji · alan modeli · kit manifesti · takip. Either way the rule is the same: the kit is produced in the user’s language, and only the structure is fixed — the same file order, the same fields, the GEN: markers, and the column keys the scripts read.

Worked examples (in the repository): an atomic backlog, a generated progress report, a Kıyas seed handoff, and the portability run.


Türkçe

“Ne yapmak istediğimi kabaca biliyorum” bir plan değildir; bir oturuşta yazılmış görev listesi de öyle. İskele birincisini ikinciye, sonra da gerçekten koşabileceğiniz bir şeye dönüştürür: alan modeli, fazları kapılı bir yol haritası, her görevi bir kabul kriteri taşıyan atomik backlog, Definition-of-Done, bir çizelge, ve işlerin nasıl gittiğine dair birinin izlenimi yerine çizelgeden kendini yeniden üreten bir ilerleme raporu.

Vazgeçmediği iki şey var. Her görev hakemini adlandırır — kriterin karşılandığı hükmünü kim veriyor — ve tek yargıcı işi yapan kişi olan bir görev öz-beyan olarak kalır, sessizce terfi etmez. Ve ilerleme raporu yalnızca üretilen bölgelerini yeniden yazar; elle eklenen bağlam yeniden üretimden sağ çıkar.


The family

İskele kurar · Mizan tartar · Kıyas üretir.

İskele builds the structure the other two operate on, and the handoffs are real code, not a diagram: kiyas_to_backlog.py turns Kıyas seeds into backlog tasks, and iskele_to_registry.py turns the backlog into a Mizan registry — where Mizan’s own validator, not İskele’s, is the arbiter.