increment SKILL.md skillA
increment from a-lottes/aspark is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add a-lottes/aspark/increment@git:20260821.b0d0761Pins git:20260821.b0d0761 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- a-lottes/aspark
- Path
skills/increment/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260821.b0d0761, committed Aug 21, 2026
- First version recorded
- Jul 13, 2026
- Size
- 3,978 bytes
- Repository stars
- 24
- License
- MIT
Start the Act phase of the SPARK loop: build the increment strictly following the approved plan, task by task, with progress tracked in the plan. Use after the plan is approved, or to fix findings that came back from /peer-review or /demo-day.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /increment — Act (Developer) You are running the **Act** ceremony — and this time *you* are the team member: the developer. No delegation; you build the increment yourself, in this conversation, so the user can watch and steer. ## Input Optional argument: the feature name. Resolve as usual. ## Steps 1. **Check the gate.** `.spark/<feature-name>/plan.md` must exist with status `approved`. If not, STOP and point to `/sprint-plan`. 2. **Load the working set — not the whole files.** From `plan.md`: §1 Architecture Decision, §2 Affected Components, §3 Task Breakdown, §4 Test Strategy. From `spec.md`: §4 User Stories with their ACs, §5 Non-Functional Requirements, §6 Out of Scope. That is your backlog, your definition of correct, and your scope fence. The rest — personas, assumptions, the clarification log, the design review, the risk table — is material the Plan phase already consumed and turned into tasks; re-reading it here buys nothing and costs the context that the tasks themselves need. Pull a further section only when a task actually calls for it. The plan is your backlog — the task table top to bottom, dependencies respected. …
Read the whole file at its exact version.
How to install
mdr add a-lottes/aspark/increment@sha256:787d9ad9baef27dbThe line at the top of this page pins the label git:20260821.b0d0761, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pei6q3khwfzsubu7)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 13, 2026 and Aug 21, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260821.b0d0761 latest | 2026-08-21 | b0d0761 | 3,978 B | A | view · diff |
| git:20260817.3d2939d | 2026-08-17 | 3d2939d | 3,727 B | A | view · diff |
| git:20260727.8eadc99 | 2026-07-27 | 8eadc99 | 3,204 B | A | view · diff |
| git:20260713.ca08cab | 2026-07-13 | ca08cab | 2,661 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3978 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
a-lottes/aspark · 24 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pei6q3khwfzsubu7 GET https://markdownregistry.com/api/v1/resolve?ref=a-lottes/aspark/increment GET https://markdownregistry.com/api/v1/blob/787d9ad9baef27dbcea83605d6af34da7c59af83f2033b1781fc8156cff2b39c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.