flow-next-capture SKILL.md skillA
flow-next-capture from gmickel/flow-next is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gmickel/flow-next/flow-next-capture@git:20261031.ad77f16Pins git:20261031.ad77f16 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gmickel/flow-next
- Path
plugins/flow-next/skills/flow-next-capture/SKILL.md- Versions recorded
- 17
- Latest version
- git:20261031.ad77f16, committed Oct 31, 2026
- First version recorded
- Aug 7, 2026
- Size
- 8,619 bytes
- Repository stars
- 718
- License
- MIT
Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create --plan-file` — agent-native, source-tagged, with a saved-spec summary and editor follow-up. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to write. Optional `--rewrite <spec-id>` overwrites an…
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
# /flow-next:capture — agent-native conversation → spec A discussion (or a `/flow-next:prospect` survivor) often holds a complete spec that never gets written down, and the next session loses it. Capture is the synthesis step: the host agent extracts the user's turns, drafts a spec against the resolved template, **tags only what it paraphrased or inferred** (`[paraphrase]` / `[inferred]` / `[strategy:<track>]`; the user's verbatim words stay untagged), writes it through flowctl, prints a compact summary, and offers the saved file in the editor ([docs/read-back.md](../../docs/read-back.md)). The capture request authorizes the write; substantive choices still get short questions. No Python synthesizer, no model subprocess. flowctl supplies thin plumbing (`spec create`, `spec set-plan`, `spec set-branch`, `memory search`) plus the `chart link-spec` callback after a chart-briefing capture. Capture never writes chart files or a chart's `ready` flag; chart never writes `.flow/specs`. Clear ideas and finished chart briefings route here; capture never manufactures a chart for clear work. Unsure: `/flow-next:flow --explain`. …
Read the whole file at its exact version.
How to install
mdr add gmickel/flow-next/flow-next-capture@sha256:0831397b844dd6f0The line at the top of this page pins the label git:20261031.ad77f16, 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_2brbucpbci5ieor4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 17 versions of this file, between Aug 7, 2026 and Oct 31, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.ad77f16 latest | 2026-10-31 | ad77f16 | 8,619 B | A | view · diff |
| git:20261016.bbb04c8 | 2026-10-16 | bbb04c8 | 8,495 B | A | view · diff |
| git:20261005.d540fd4 | 2026-10-05 | d540fd4 | 7,854 B | A | view · diff |
| git:20261001.cc1d846 | 2026-10-01 | cc1d846 | 7,909 B | A | view · diff |
| git:20261001.fc74d31 | 2026-10-01 | fc74d31 | 9,051 B | A | view · diff |
| git:20260929.1313198 | 2026-09-29 | 1313198 | 9,018 B | A | view · diff |
| git:20260929.55729da | 2026-09-29 | 55729da | 9,107 B | A | view · diff |
| git:20260928.09529bc | 2026-09-28 | 09529bc | 14,833 B | A | view · diff |
| git:20260926.e553583 | 2026-09-26 | e553583 | 14,957 B | A | view · diff |
| git:20260918.38236fa | 2026-09-18 | 38236fa | 14,981 B | A | view · diff |
| git:20260912.3716e52 | 2026-09-12 | 3716e52 | 14,884 B | A | view · diff |
| git:20260911.f92da65 | 2026-09-11 | f92da65 | 14,909 B | A | view · diff |
| git:20260901.d8667c9 | 2026-09-01 | d8667c9 | 14,190 B | A | view · diff |
| git:20260831.8e45afc | 2026-08-31 | 8e45afc | 13,501 B | A | view · diff |
| git:20260815.bfe5cd9 | 2026-08-15 | bfe5cd9 | 13,115 B | A | view · diff |
| git:20260808.4f6600e | 2026-08-08 | 4f6600e | 12,880 B | A | view · diff |
| git:20260807.e8610ba | 2026-08-07 | e8610ba | 19,971 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 (8619 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
gmickel/flow-next · 718 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2brbucpbci5ieor4 GET https://markdownregistry.com/api/v1/resolve?ref=gmickel/flow-next/flow-next-capture GET https://markdownregistry.com/api/v1/blob/0831397b844dd6f05e15f0eba145e14fd48e68b89e0bb94e1aabf4e1cc7e5b8e
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.
More from gmickel/flow-next
Every file in gmickel/flow-next