Skip to content
Skills Library
Programming · Automation

improve-loop

/improve-loop

Autonomous loop that works through docs/STORIES.md one story at a time for a Windows app, building, snapshotting, comparing against reference screenshots, fixing, and committing, until a milestone is done. Use when the user says "keep going", "work through the backlog", or wants an unattended improvement loop.

Repository
Phan-Tee ↗
Licence
MIT
Last repository change
02.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Autonomous loop that works through docs/STORIES.md one story at a time for a Windows app, building, snapshotting, comparing against reference screenshots, fixing, and committing, until a milestone is done. Use when the user says "keep going", "work through the backlog", or wants an unattended improvement loop.

Triggers from the description

keep goingwork through the backlog

Arguments

/improve-loop [milestone, e.g. M1]
Original author description

Autonomous loop that works through docs/STORIES.md one story at a time for a Windows app, building, snapshotting, comparing against reference screenshots, fixing, and committing, until a milestone is done. Use when the user says "keep going", "work through the backlog", or wants an unattended improvement loop.

How it works

  1. 1. Pick
  2. 2. Plan
  3. 3. Code
  4. 4. Build and Snapshot
  5. 5. Compare
  6. 6. Commit and Record
  7. 7. Report
  8. Done when
Original SKILL.md headings · 62 lines, 247 words
SKILL.md preview
---
name: improve-loop
description: Autonomous loop that works through docs/STORIES.md one story at a time for a Windows app, building, snapshotting, comparing against reference screenshots, fixing, and committing, until a milestone is done. Use when the user says "keep going", "work through the backlog", or wants an unattended improvement loop.
argument-hint: "[milestone, e.g. M1]"
---

# Improve loop

One pass through the loop takes one story from `todo` to `done`:

```text
pick story -> plan -> code -> .\build.ps1 -> .\tools\snap.ps1 -> compare -> fix -> commit -> update STORIES.md
```

Stop after the milestone the user named (default: current milestone), then report.

## 1. Pick

Open `docs/STORIES.md`. Take the first `todo` story in the current
milestone whose dependencies are `done`. Set it to `doing`.

## 2. Plan

Write two to five lines before editing code: which files change, which
models need new fields, and which snapshot page will verify it.

## 3. Code

Follow `csharp-winui` and `win-design`. Keep logic in `<AppName>Core` and
views in `<AppName>`.

## 4. Build and Snapshot

```powershell
.\build.ps1
.\tools\snap.ps1
```

If the story has logic, add a unit test or self-test check (`test-win-app`).

## 5. Compare

Inspect your snapshot alongside reference screenshots or acceptance criteria:
1. Missing or wrong behavior from acceptance criteria.
2. Words and flow (Windows sentence case, native controls).
3. Layout alignment and grid checks (`tools\grid-lint.ps1`).

Fix and snapshot again (maximum 3 iterations per story).

## 6. Commit and Record

```powershell
git add -A
git commit -m "Complete task with Ctrl+Enter"
```

Update the story to `done` in `docs/STORIES.md`. One story per commit.

## 7. Report

Report stories done, snapshot image paths, and run `.\build.ps1 -Open` so
the user can test the build.

## Done when

All stories in the milestone are committed, snapshots are verified, and `build.ps1 -Open` runs cleanly for the user.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · MinnThikeTunn/Phan-Tee100MIT
daveebbelaar/bama100MIT
daveebbelaar/bawa100MIT
Stijnus/dsh-rev-eng100MIT

Database snapshot: 13.11.2026 · package version fedcce279cc6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100user-stories
    Prioritized backlog of user stories with checkable acceptance criteria (docs/STORIES.md) for a Windows app, built from a brief, research, or screen index. Use after app-brief or clone, or when the user asks for user stories, a backlog, a feature list, or "what do we build first".
  • 100research
    Online research for a Windows app before building it, run as parallel researcher subagents, saved to docs/research/. Use when the user asks what to build, which features matter, how the best apps in a category work, how a Windows API or integration works, or wants a feature comparison.
  • 100generate-readme-screenshots
    Regenerate high-resolution README screenshots from Storybook stories. Use this skill when visual diffs are detected in any story under "Docs/README Screenshots", or when story data/layout changes require updated documentation assets. Triggers on: visual regressions in readme…
  • 100user-stories
    Turn a brief or screen index into a backlog (docs/STORIES.md) for a Windows app, with checkable acceptance criteria, organized in milestones. Use when the brief is done, or before writing code.
  • 98windows-sandbox-interactive
    Explore and drive a Windows app step by step in a live Windows Sandbox with UI Automation, screenshots, commands and system snapshots. Use for multi-step UI testing, reproducing a bug by hand, trying prerequisites one at a time, or finding out what an action changed on the system.
  • 84work-loop
    Drain the work-item backlog as a self-paced autonomous loop, launched via /loop: each cycle triages raw intake, admits items through the fail-closed work-class gate, runs them through /work-items:work under an adaptive cap, and checks the drain exit. Authors PRs, never merges.…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.