next-steps SKILL.md skillA
next-steps 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/next-steps@git:20261028.50d2efbPins git:20261028.50d2efb 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/next-steps/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261028.50d2efb, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 10,098 bytes
- Repository stars
- 24
- License
- MIT
Have the Product Owner survey the project's current state — shipped features, in-flight work, open findings, standing goals — and propose one concrete next feature ready to hand to /story-time or /spark. Use when the user has no idea in hand and asks "what should we build next", when a loop just closed and the next cycle needs a starting point, or when the backlog feels stale and needs a grounded suggestion instead of a guess.
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
# /next-steps — Propose the Next Feature (Product Owner)
You are running an **advisory** ceremony, not a gated one. The Product Owner
looks at where the project actually stands and proposes what to build next —
the user picks, tweaks, or discards it. Nothing here gets written to
`.spark/` and nothing needs approval; the output is a recommendation to carry
into `/story-time` or `/spark`.
## Input
None required. Optionally the user may point at a theme or constraint (e.g.
"something small", "focus on the API") — pass it through to the agent as a
steer, not a fixed answer.
## Steps
1. **Gather the loop state yourself — don't delegate this.** The
`product-owner` agent cannot run `git` or walk `.spark/`. Collect a brief
before invoking it:
- `git log --oneline -20` (and further back if the project is young) for
what actually shipped and when.
- Every `.spark/<feature-name>/` directory: for `spec.md`, `plan.md`,
`review.md`, `qa.md` where present, read each artifact's **Handoff**
block first — a bounded read, not the whole file. Status, Summary/
Verdict and Open items are enough to classify the feature as
…Read the whole file at its exact version.
How to install
mdr add a-lottes/aspark/next-steps@sha256:de39a80914f7f8d1The line at the top of this page pins the label git:20261028.50d2efb, 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_futjbahiumcyhgdl)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Jul 17, 2026 and Oct 28, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.50d2efb latest | 2026-10-28 | 50d2efb | 10,098 B | A | view · diff |
| git:20261028.ccbfe4a | 2026-10-28 | ccbfe4a | 10,069 B | A | view · diff |
| git:20261028.6b10800 | 2026-10-28 | 6b10800 | 10,064 B | A | view · diff |
| git:20261028.7ece7f7 | 2026-10-28 | 7ece7f7 | 9,957 B | A | view · diff |
| git:20261028.64767bc | 2026-10-28 | 64767bc | 9,360 B | A | view · diff |
| git:20261025.4d6c4ac | 2026-10-25 | 4d6c4ac | 6,384 B | A | view · diff |
| git:20260919.180f23c | 2026-09-19 | 180f23c | 6,249 B | A | view · diff |
| git:20260817.3d2939d | 2026-08-17 | 3d2939d | 4,935 B | A | view · diff |
| git:20260806.f7d13e6 | 2026-08-06 | f7d13e6 | 4,698 B | A | view · diff |
| git:20260717.6a1b4d5 | 2026-07-17 | 6a1b4d5 | 4,599 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 (10098 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_futjbahiumcyhgdl GET https://markdownregistry.com/api/v1/resolve?ref=a-lottes/aspark/next-steps GET https://markdownregistry.com/api/v1/blob/de39a80914f7f8d1047748839e5adeada25d07f82fa6f00f6e8b6aa3f4703ac3
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.