nested-metadata

Fixture mirroring the task-spec skill's frontmatter shape: a literal block-scalar description spanning several indented lines, followed by a nested metadata map with a quoted version string.

Aller à l'installation

Dépôt: luanmorenommaciel/converge
Dernière activité de la source: 28 juillet 2026 à 18:58
Langue détectée de SKILL.md: anglais
Étoiles: 19
Forks: 52

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/luanmorenommaciel/converge --skill nested-metadata

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

evidence-to-next-pass

Converge descent conductor — derives the current and next pass from workspace evidence, enforces order with fail-closed pre/post hooks, and hands the agent the owning pass prompt. Use when someone asks "what's next", "where are we", "continue", "start pass N", "guide me through Converge", or requests a step-by-step or guided chat. In guided chat, present the stable choices from `cvg next --guided` and wait at every pass boundary; never infer CONTINUE. Run the pre-hook first, the pass prompt second, and the post-hook plus authoritative gate last. Do NOT use this skill to waive a gate, treat evidence presence as a verdict, or pick a lane (`cvg lane` owns that).

2026-08-28

brd-docs-to-tech-req

Transforms a client BRD (cvg/docs/brd/|.pdf) into a verifiable tech-spec (cvg/docs/tech-spec/) — the engineering solution shape for the client's problem. Implements Converge Pass 1 (Intent), the top of the chain. Use when a brief has landed and someone says "turn this brief into a tech-spec", "start Converge pass 1", or "what are we actually building here". Runs the Understand / Prior-art / Interrogate (frontier rounds with recommended defaults, gap register) / Crystallize steps and gates on restating the problem in one paragraph AND the spec answers it, every requirement falsifiable and prioritized, success metrics traced to the BRD's KPIs, no unresolved blocker gaps. Stays above the stack — no schema, no engine choice. Do NOT use for architecture or stack decisions (that is Pass 3), when a signed-off tech-spec already exists (go to Pass 2, tech-req-to-adrs), or when no BRD exists at all (run Pass 0, idea-to-brd, to capture the brief first). Engine/format bound via flags, never baked into the name.

2026-08-16

idea-to-brd

Converge Pass 0 (Capture) — optional, like Register (Pass 6). Turns a raw idea with no client brief — a founder thought, an internal itch, a voice-note transcript — into a BRD (cvg/docs/brd/ or .pdf) written in the owner's voice, so Pass 1 can consume it unchanged — or into a no-go record when the pain doesn't justify a build. Use when someone says "I have an idea", "capture this idea", "write the brief", "grill me about this idea", or "start Converge pass 0". Runs Scope-check / Grill (frontier rounds — every unblocked question at once with defaults, one reply per round; facts looked up, do-nothing cost probed, pre-mortem run) / Draft / Self-review and gates on the pain carrying a provenance-tagged number, at least one KPI in the owner's terms, in/out scope each non-empty, and every open question owned. Produces the brief, NEVER the spec — no requirements, no solution shape, no technology. Do NOT use when a BRD exists (enter at Pass 1) or to write a tech-spec (that IS Pass 1).

2026-08-16

Tout voir dans ce dépôt

nested-metadata

Options d'installation

Vérifiez les fichiers source

Nested Metadata

Nested Metadata

name	nested-metadata
description	Fixture mirroring the task-spec skill's frontmatter shape: a literal block-scalar description spanning several indented lines, followed by a nested metadata map with a quoted version string.
metadata	{"version":"3.6.0"}

nested-metadata

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Nested Metadata

Plus depuis ce dépôt

Nested Metadata