kharmanskyi/open-steps

Skills that keep development open to the person running it, who does not read code: plain-language session reports, followable operator instructions, decisions framed as questions with a recommendation, an attack on a decision while it can still be changed, what-to-do-next orchestration, verification of work done in other sessions, and on-demand restatement of any text in plain words.