[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AW7AX7MH2S7GSG6JAD4PQY":3,"skill-same:01M7AW7AX7MH2S7GSG6JAD4PQY":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AW7AX7MH2S7GSG6JAD4PQY","yun-write-spec",null,"Write the spec — consolidate a large task's settled decisions into one durable document before it is sliced into tickets. Use when the decisions are settled and the user wants them written up, or says \"write the spec\" \u002F \"escribí el spec\". Declines small fixes that need no spec.","matiinchauspe\u002Fyunque","matiinchauspe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7861346?v=4","01M7AW106HSV1DVWJSQQBD6BYB","Matias","01M7AW107JZVCTQHZEED16N5PZ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: yun-write-spec\ndescription: Write the spec — consolidate a large task's settled decisions into one durable document before it is sliced into tickets. Use when the decisions are settled and the user wants them written up, or says \"write the spec\" \u002F \"escribí el spec\". Declines small fixes that need no spec.\n---\n\n# yun-write-spec\n\nA spec is written by **synthesis, not interview**. Everything already decided — in this\nconversation and in the decisions `yun-grill-plan` persisted — gets consolidated into one\ndurable document. You ask the user **nothing**: if a decision is still open, you don't\nwrite, you surface it.\n\n## Guard — two gates before you synthesize\n\nA spec is a commitment artifact. Pass both gates before writing a line.\n\n- **Magnitude.** Does this task warrant a spec at all? A task that crosses more than one\n  component, or is too big for a single session, is **large** and earns a spec. A small fix\n  — one bug, a change to a single component within a single session — does not: say so and\n  stop, the work goes straight to implementation.\n- **Ripeness.** Are the decisions settled? `recall` prior decisions on the task's keywords\n  (`skills\u002F_shared\u002Fmemory-convention.md`). A blocking decision still open means the\n  conversation is not **ripe** — surface those decisions and hand back to `yun-grill-plan`\n  rather than write a half-spec. Where recall is unavailable or returns nothing, judge\n  ripeness from the conversation alone — an empty recall is not proof of ripeness, so don't\n  bounce a task back to `yun-grill-plan` on missing memory.\n\nDone when the task is confirmed large **and** every blocking decision is settled.\n\n## Steps\n\n### 1. Gather context — no interview\n\nPull the whole picture together: the conversation, plus the decisions `yun-grill-plan`\npersisted (`recall` via `skills\u002F_shared\u002Fmemory-convention.md`). When the task was charted by\n`yun-chart-course`, also `fetch` the `map` kind (`skills\u002F_shared\u002Fartifact-convention.md`) and\nfollow its **Decisions so far** links to the resolved decision tickets — the map is an index,\nso the decisions themselves live in the tickets, not the one-line gists. Any fact you can find\nby exploring the codebase, look up rather than ask. `consult` the project's domain model\n(`skills\u002F_shared\u002Fdomain-convention.md`): the spec is where every downstream ticket, branch and\ncommit inherits its names, so write it in the **ubiquitous language**, and surface a solution\nthat contradicts an ADR rather than writing past it. Synthesis only — the user answers nothing.\nDone when every settled decision, and the domain model where there is one, is in front of you.\n\n### 2. Sketch the testing seams\n\nDecide **where the feature gets tested** — its **testing seams** — before writing. Prefer a\nseam that already exists to a new one. Use the **highest** seam that still covers the\nbehaviour, and the **fewest** — the ideal number is one. These become the Testing Decisions section,\nand they are the anchor `yun-slice-plan`'s tracer bullets verify against. Done when every\nbehaviour the spec will describe has a named seam.\n\n### 3. Write the spec\n\nFill the template by synthesis. Implementation Decisions is where grill-plan's persisted\ndecisions land consolidated; Testing Decisions carries the seams from step 2; Further Notes\nholds only non-blocking residuals — anything blocking was caught by the guard. Every other\nsection — Problem, Solution, User Stories, Out of Scope — traces to the conversation and the\npersisted decisions directly.\n\n\u003Cspec-template>\n\n# \u003CFeature title>\n\n**Problem** — what's missing or broken, from the user's perspective.\n\n**Solution** — the approach chosen to solve it.\n\n**User Stories** — the behaviours this delivers, each from the user's perspective.\n\n**Implementation Decisions** — the settled technical decisions, consolidated.\n\n**Testing Decisions** — the seam(s) the feature is tested at, from step 2.\n\n**Out of Scope** — the non-goals, named explicitly.\n\n**Further Notes** — residual, non-blocking context.\n\n\u003C\u002Fspec-template>\n\nDone when every section traces to something already decided — no invention.\n\n### 4. Publish the spec\n\n`publish` the spec as the `spec` kind through `skills\u002F_shared\u002Fartifact-convention.md`; the\nconvention decides where it lands and under which key. `yun-slice-plan` will `fetch` it from\nthere. Done when the spec is published and its location is known.\n\n## Attribution\n\nAdapted for this workspace from **Matt Pocock's `to-spec`** (github.com\u002Fmattpocock\u002Fskills,\nMIT). Changes: added the two-gate guard (magnitude + ripeness) so it fires\nautonomously without producing a premature spec; `recall` and `publish` route through the\nmemory- and artifact-conventions instead of a `setup`-bound tracker, so the skill never\nnames a tracker; the spec publishes as the `spec` artifact kind alongside `yun-slice-plan`'s\ntickets. The highest\u002Ffewest-seam testing framing and the seven-section template are\npreserved from the source.\n","# yun-write-spec\n\nA spec is written by **synthesis, not interview**. Everything already decided — in this\nconversation and in the decisions `yun-grill-plan` persisted — gets consolidated into one\ndurable document. You ask the user **nothing**: if a decision is still open, you don't\nwrite, you surface it.\n\n## Guard — two gates before you synthesize\n\nA spec is a commitment artifact. Pass both gates before writing a line.\n\n- **Magnitude.** Does this task warrant a spec at all? A task that crosses more than one\n  component, or is too big for a single session, is **large** and earns a spec. A small fix\n  — one bug, a change to a single component within a single session — does not: say so and\n  stop, the work goes straight to implementation.\n- **Ripeness.** Are the decisions settled? `recall` prior decisions on the task's keywords\n  (`skills\u002F_shared\u002Fmemory-convention.md`). A blocking decision still open means the\n  conversation is not **ripe** — surface those decisions and hand back to `yun-grill-plan`\n  rather than write a half-spec. Where recall is unavailable or returns nothing, judge\n  ripeness from the conversation alone — an empty recall is not proof of ripeness, so don't\n  bounce a task back to `yun-grill-plan` on missing memory.\n\nDone when the task is confirmed large **and** every blocking decision is settled.\n\n## Steps\n\n### 1. Gather context — no interview\n\nPull the whole picture together: the conversation, plus the decisions `yun-grill-plan`\npersisted (`recall` via `skills\u002F_shared\u002Fmemory-convention.md`). When the task was charted by\n`yun-chart-course`, also `fetch` the `map` kind (`skills\u002F_shared\u002Fartifact-convention.md`) and\nfollow its **Decisions so far** links to the resolved decision tickets — the map is an index,\nso the decisions themselves live in the tickets, not the one-line gists. Any fact you can find\nby exploring the codebase, look up rather than ask. `consult` the project's domain model\n(`skills\u002F_shared\u002Fdomain-convention.md`): the spec is where every downstream ticket, branch and\ncommit inherits its names, so write it in the **ubiquitous language**, and surface a solution\nthat contradicts an ADR rather than writing past it. Synthesis only — the user answers nothing.\nDone when every settled decision, and the domain model where there is one, is in front of you.\n\n### 2. Sketch the testing seams\n\nDecide **where the feature gets tested** — its **testing seams** — before writing. Prefer a\nseam that already exists to a new one. Use the **highest** seam that still covers the\nbehaviour, and the **fewest** — the ideal number is one. These become the Testing Decisions section,\nand they are the anchor `yun-slice-plan`'s tracer bullets verify against. Done when every\nbehaviour the spec will describe has a named seam.\n\n### 3. Write the spec\n\nFill the template by synthesis. Implementation Decisions is where grill-plan's persisted\ndecisions land consolidated; Testing Decisions carries the seams from step 2; Further Notes\nholds only non-blocking residuals — anything blocking was caught by the guard. Every other\nsection — Problem, Solution, User Stories, Out of Scope — traces to the conversation and the\npersisted decisions directly.\n\n\u003Cspec-template>\n\n# \u003CFeature title>\n\n**Problem** — what's missing or broken, from the user's perspective.\n\n**Solution** — the approach chosen to solve it.\n\n**User Stories** — the behaviours this delivers, each from the user's perspective.\n\n**Implementation Decisions** — the settled technical decisions, consolidated.\n\n**Testing Decisions** — the seam(s) the feature is tested at, from step 2.\n\n**Out of Scope** — the non-goals, named explicitly.\n\n**Further Notes** — residual, non-blocking context.\n\n\u003C\u002Fspec-template>\n\nDone when every section traces to something already decided — no invention.\n\n### 4. Publish the spec\n\n`publish` the spec as the `spec` kind through `skills\u002F_shared\u002Fartifact-convention.md`; the\nconvention decides where it lands and under which key. `yun-slice-plan` will `fetch` it from\nthere. Done when the spec is published and its location is known.\n\n## Attribution\n\nAdapted for this workspace from **Matt Pocock's `to-spec`** (github.com\u002Fmattpocock\u002Fskills,\nMIT). Changes: added the two-gate guard (magnitude + ripeness) so it fires\nautonomously without producing a premature spec; `recall` and `publish` route through the\nmemory- and artifact-conventions instead of a `setup`-bound tracker, so the skill never\nnames a tracker; the spec publishes as the `spec` artifact kind alongside `yun-slice-plan`'s\ntickets. The highest\u002Ffewest-seam testing framing and the seven-section template are\npreserved from the source.\n",{"name":5,"description":7},"main","31bfd2af63052d9bb7036b02364637ba5dc70f87","skills\u002Fyun-write-spec",0,"https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe","The fools will be invencible - \r\n\r\nDevelop developing thoughts","2026-11-13 04:14:30",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add matiinchauspe\u002Fyunque --skill yun-write-spec",{"tool":38,"command":39},"bunx","bunx skills add matiinchauspe\u002Fyunque --skill yun-write-spec",{"tool":41,"command":42},"pnpm","pnpm dlx skills add matiinchauspe\u002Fyunque --skill yun-write-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-spec\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AW7HDMMJ372HG8PGM5RR0Z","yun-write-wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-wizard\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AW76CY32E072H8FKE8PDQ5","yun-write-pr","Write a pull request title and body that show the change — its ticket, its shape, the evidence it works, and how dangerous it is to merge.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-pr\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AW7291YQKHYGSJKGG1EVVX","yun-write-handoff","Compact the current session into a disposable handoff baton for the next agent, pointing at durable memory instead of duplicating it.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-handoff\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AW6WXBGGYX7XMWYQFMNCVJ","yun-write-agent-docs","Use when authoring or editing a document an agent reads in this workspace — a skill, a `skills\u002F_shared\u002F` contract, `AGENTS.md` or `skills\u002FREADME.md` — deciding how it is invoked, what lives in it versus a linked file, naming it, or diagnosing why a skill misfires, bloats, or fires unreliably.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-agent-docs\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AW6Q9K91GDDWY0YJMCYSJK","yun-tdd","Test-driven development — the red → green loop, tests written only at pre-agreed seams. Use when the user wants to build a feature or fix a bug test-first, or mentions TDD or red-green. Reached by the implement flow to drive a build at a seam.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-tdd\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AW6KB515QS77NVG97B6C0A","yun-sync-repo","Bring an external repo into the workspace as work material — cloned into repos\u002F\u003Cname>\u002F, gitignored, with its own .git.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-sync-repo\u002FSKILL.md",[],[]]