[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71W165EASA6P1YS8GMPJD4F":3,"skill-same:01M71W165EASA6P1YS8GMPJD4F":57},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M71W165EASA6P1YS8GMPJD4F","to-spec",null,"Turn the current conversation into a spec and publish it to the technical backlog — no interview, just synthesis of what you've already discussed.","Loulen\u002Fprompt-driven-orchestrator","Loulen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38249550?v=4","01M71VZRF4D30PYHNZ45KXHZ1V","Louis Lenoir","01M71VZRG4TFXSV0QVXPVDZB1B",20,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLoulen\u002Fprompt-driven-orchestrator\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"to spec","spec","conversation","interview","just","backlog","true","technical","you","publish","it","Synthesis","2026-11-10 13:02:02",false,"---\nname: to-spec\ndescription: Turn the current conversation into a spec and publish it to the technical backlog — no interview, just synthesis of what you've already discussed.\n---\n\nThis skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you (in `docs\u002Fagents\u002F`) — run `\u002Fbuild-factory` if not.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n- How the feature sits in the test pyramid, including its apex — the **agentic test** layer (a subagent drives the real running system through its primary surface — UI, CLI, warehouse). Each ticket from `\u002Fto-tickets` carries an executable **Feature Path (FP)** as its auto-merge gate; cross-cutting nominal journeys may be promoted to a **Happy Path (HP)**. See the `agentic-tests` skill.\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n","This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you (in `docs\u002Fagents\u002F`) — run `\u002Fbuild-factory` if not.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n- How the feature sits in the test pyramid, including its apex — the **agentic test** layer (a subagent drives the real running system through its primary surface — UI, CLI, warehouse). Each ticket from `\u002Fto-tickets` carries an executable **Feature Path (FP)** as its auto-merge gate; cross-cutting nominal journeys may be promoted to a **Happy Path (HP)**. See the `agentic-tests` skill.\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n",{"name":5,"description":7},"main","2b4a893ced882539a0c35ce732ab459e404da6c5",".agents\u002Fskills\u002Fto-spec",7,"https:\u002F\u002Fgithub.com\u002FLoulen\u002Fprompt-driven-orchestrator","https:\u002F\u002Fgithub.com\u002FLoulen","2026-11-12 21:53:30",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Loulen\u002Fprompt-driven-orchestrator --skill to-spec",{"tool":49,"command":50},"bunx","bunx skills add Loulen\u002Fprompt-driven-orchestrator --skill to-spec",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Loulen\u002Fprompt-driven-orchestrator --skill to-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLoulen\u002Fprompt-driven-orchestrator\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",true,[],[58,78,99],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":31},"01M71W1970610MAC2ZS50W1M5B","to-tickets","Break a plan, spec, or the current conversation into vertical-slice tickets on the technical backlog, each declaring its blocking edges — text in one file per ticket locally, or native blocking links on GitHub\u002FGitLab.","https:\u002F\u002Fgithub.com\u002FLoulen\u002Fprompt-driven-orchestrator\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[65,66,67,21,20,68,24,69,25,26,70,71,72,73,74,75,76,77],"to tickets","tickets","links","slice","ticket","file","one","text","plan","gitlab","github","native","break",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":31},"01M71W0XA5GTYJMPQBEZCD0D95","implement","Implement a spec or set of tickets by orchestrating a tdd role, an independent code-review role, and an agentic-tests role in a loop until build, tests, and the Feature Path are green with no blocking finding.","https:\u002F\u002Fgithub.com\u002FLoulen\u002Fprompt-driven-orchestrator\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplement\u002FSKILL.md",[],[80,85,86,87,20,66,88,89,90,91,92,93,25,94,95,96,97,98],"with","path","role","tdd","build","review","SET","green","feature","tests","loop","agentic","code","code-review",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":31},"01M71W0R4GABV4QPA9PDM6W6GP","grill-with-docs","Per-story grilling that stress-tests your plan against the project's domain model, sharpens terminology, and writes CONTEXT.md\u002FADRs inline as decisions crystallise. Run it when designing a business user story before slicing it into work.","https:\u002F\u002Fgithub.com\u002FLoulen\u002Fprompt-driven-orchestrator\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[85,106,107,108,109,110,111,112,113,114,25,94,115,116,117,118,73,119,120,121],"grill","docs","grill with docs","inline","user story","as","domain","model","project","business","when","decisions","work","terminology","run","domain model"]