[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD0PX7F9C5A2YNW71THFX1":3,"skill-same:01M6MD0PX7F9C5A2YNW71THFX1":78},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":45,"ownerDescription":47,"updatedAt":48,"install":49,"resources":61},"01M6MD0PX7F9C5A2YNW71THFX1","cy-issue-to-spec",null,"Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.","compozy\u002Fcompozy","compozy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F205107042?v=4","01M6JWVTXX4DX38AWZ7SPFEKEV","CompozyOS","01M6JWVV2P34GM1PDATVB2EV05",2871,"MIT","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcy-issue-to-spec\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,9,32],"spec","to spec","issue","issue to spec","cy issue to spec","github","linear","SET","first","pair","it","number","true","bare","2026-11-10 10:12:30",false,"---\nname: cy-issue-to-spec\ndescription: >-\n  Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub +\n  Linear issue pair — or starts from a bare issue and authors the spec first.\ndisable-model-invocation: true\nargument-hint: \"[spec slug or issue number]\"\n---\n\n# Issue ↔ Spec\n\nOne feature lives in three places: the working **spec set** under `.compozy\u002Ftasks\u002F\u003Cslug>\u002F`, its published folder in the `compozy\u002Fcompozy-specs` repo, and its **mirror** — a GitHub issue and a Linear issue that read identically. This skill moves a feature between those places and leaves all three agreeing.\n\n## Branches\n\n| Starting point | Enter at |\n| --- | --- |\n| A spec set already exists under `.compozy\u002Ftasks\u002F\u003Cslug>\u002F` | Step 1 |\n| A GitHub issue exists carrying no spec behind it | Step 0 |\n\n## Step 0 — Author the spec\n\nOnly when starting from a bare issue.\n\nRead the issue and restate its scope in one sentence. When it bundles separable features, split it first: retitle the original to the narrower scope, open a second issue for the remainder, and cross-link both — then spec one of them.\n\nActivate `cy-create-spec` with `docs\u002F_memory\u002Fspec-authoring-playbook.md`. It writes `_slices.md` and offers peer review after the user approves the spec.\n\n*Done when:* `.compozy\u002Ftasks\u002F\u003Cslug>\u002F` holds `_spec.md` (or `_prd.md` + `_techspec.md`), its companions, `adrs\u002F`, and `_slices.md`, and the user has approved the spec.\n\n## Step 1 — Stage the spec set\n\nRun the staging helper (**mutating** — writes into the specs repo working tree):\n\n```bash\npython3 .agents\u002Fskills\u002Fcy-issue-to-spec\u002Fscripts\u002Fpublish-spec.py \\\n  --spec-dir .compozy\u002Ftasks\u002F\u003Cslug> \\\n  --specs-repo \u003Cspecs-repo-checkout> \\\n  --repo-root \"$(pwd)\"\n```\n\nIt publishes `_*.md`, `task_NN.md`, and `adrs\u002F*.md`; it leaves `analysis\u002F`, `qa\u002F`, `memory\u002F`, `evidence\u002F`, `reviews-*\u002F`, `state.yaml`, and handoff notes in the workspace. Pass `--include '\u003Cglob>'` for a document that carries spec content under a name outside those patterns, and `--archived` when the workstream is already closed.\n\nThe folder is named `YYYY-MM-DD-\u003Cslug>`, dated by when the work began: the source folder's own date prefix when it carries one, else `state.yaml`'s `created_at`, else the earliest document. Active specs sit at the repo root; closed ones under `_archived\u002F`.\n\n*Done when:* the helper exits 0, reporting the staged path, file count, and a clean scan.\n\n## Step 2 — Resolve the report\n\nThe helper scrubs machine-local paths and repairs `..\u002Fadrs\u002F` links itself. Two findings need a decision:\n\n- **A surviving local path or a possible secret** exits the helper non-zero. Edit the staged document, then re-run the scan.\n- **A broken relative link** points at something the filter left behind. Either publish that material too, or accept the dangling reference — the repo README already tells readers that older documents point at files they will not find.\n\n*Done when:* every reported path, secret, and link is fixed or consciously accepted.\n\n## Step 3 — Index and push\n\nAdd one row to the specs repo `README.md`, in the **Active** or **Archived** table: the folder link, one sentence on what the spec covers, the tracking-issue link, and the `Documents` column naming its shape (`spec`, `prd + techspec`, `brief + techspec`, …). Newest first.\n\nCommit as `docs: add \u003Cslug> spec set` and push.\n\n*Done when:* every relative link in the README resolves and the commit is on `main`.\n\n## Step 4 — Write the issue body\n\nRead `.agents\u002Fskills\u002Fcy-issue-to-spec\u002Freferences\u002Fissue-body.md` in full and build the body against it.\n\n*Done when:* the body opens with the spec-set link block and every section of the skeleton is either written or deliberately absent.\n\n## Step 5 — Open the mirror\n\nCreate or update the GitHub issue: title matching the spec's subject, labels `roadmap` + `planned` (removing `needs-plan`), the Step 4 body, and a closing `Roadmap item tracked in Linear: [CY-NNN](…)` line.\n\nCreate or update the Linear issue with the same title and the same body, swapping the footer for `Tracked on GitHub: \u003Curl>`. Linear renders GitHub callout syntax as plain text — convert a `> [!NOTE]` block to a bold sentence.\n\nVerify with the audit helper (**read-only**):\n\n```bash\npython3 .agents\u002Fskills\u002Fcy-issue-to-spec\u002Fscripts\u002Fcheck-tracker-sync.py --linear-json \u003Cexport>\n```\n\nSave the Linear MCP `list_issues` result to a file first; without `--linear-json` the helper audits only the GitHub half.\n\n*Done when:* the helper exits 0 with no defects, and both issues carry a link to each other.\n\n## Reference\n\n- Publishing an already-archived spec skips Step 0 and Step 4's tracking link when no issue exists — the README row is then the only index entry.\n- Renaming a published folder breaks the links already sitting in both trackers; update the issue bodies in the same change.\n- `references\u002Fissue-body.md` — the issue-body skeleton and where each part comes from in the spec.\n- `scripts\u002Fpublish-spec.py` — **mutating**; stages, scrubs, scans, and link-checks a spec set.\n- `scripts\u002Fcheck-tracker-sync.py` — **read-only**; audits titles, states, and links across the mirror.\n","# Issue ↔ Spec\n\nOne feature lives in three places: the working **spec set** under `.compozy\u002Ftasks\u002F\u003Cslug>\u002F`, its published folder in the `compozy\u002Fcompozy-specs` repo, and its **mirror** — a GitHub issue and a Linear issue that read identically. This skill moves a feature between those places and leaves all three agreeing.\n\n## Branches\n\n| Starting point | Enter at |\n| --- | --- |\n| A spec set already exists under `.compozy\u002Ftasks\u002F\u003Cslug>\u002F` | Step 1 |\n| A GitHub issue exists carrying no spec behind it | Step 0 |\n\n## Step 0 — Author the spec\n\nOnly when starting from a bare issue.\n\nRead the issue and restate its scope in one sentence. When it bundles separable features, split it first: retitle the original to the narrower scope, open a second issue for the remainder, and cross-link both — then spec one of them.\n\nActivate `cy-create-spec` with `docs\u002F_memory\u002Fspec-authoring-playbook.md`. It writes `_slices.md` and offers peer review after the user approves the spec.\n\n*Done when:* `.compozy\u002Ftasks\u002F\u003Cslug>\u002F` holds `_spec.md` (or `_prd.md` + `_techspec.md`), its companions, `adrs\u002F`, and `_slices.md`, and the user has approved the spec.\n\n## Step 1 — Stage the spec set\n\nRun the staging helper (**mutating** — writes into the specs repo working tree):\n\n```bash\npython3 .agents\u002Fskills\u002Fcy-issue-to-spec\u002Fscripts\u002Fpublish-spec.py \\\n  --spec-dir .compozy\u002Ftasks\u002F\u003Cslug> \\\n  --specs-repo \u003Cspecs-repo-checkout> \\\n  --repo-root \"$(pwd)\"\n```\n\nIt publishes `_*.md`, `task_NN.md`, and `adrs\u002F*.md`; it leaves `analysis\u002F`, `qa\u002F`, `memory\u002F`, `evidence\u002F`, `reviews-*\u002F`, `state.yaml`, and handoff notes in the workspace. Pass `--include '\u003Cglob>'` for a document that carries spec content under a name outside those patterns, and `--archived` when the workstream is already closed.\n\nThe folder is named `YYYY-MM-DD-\u003Cslug>`, dated by when the work began: the source folder's own date prefix when it carries one, else `state.yaml`'s `created_at`, else the earliest document. Active specs sit at the repo root; closed ones under `_archived\u002F`.\n\n*Done when:* the helper exits 0, reporting the staged path, file count, and a clean scan.\n\n## Step 2 — Resolve the report\n\nThe helper scrubs machine-local paths and repairs `..\u002Fadrs\u002F` links itself. Two findings need a decision:\n\n- **A surviving local path or a possible secret** exits the helper non-zero. Edit the staged document, then re-run the scan.\n- **A broken relative link** points at something the filter left behind. Either publish that material too, or accept the dangling reference — the repo README already tells readers that older documents point at files they will not find.\n\n*Done when:* every reported path, secret, and link is fixed or consciously accepted.\n\n## Step 3 — Index and push\n\nAdd one row to the specs repo `README.md`, in the **Active** or **Archived** table: the folder link, one sentence on what the spec covers, the tracking-issue link, and the `Documents` column naming its shape (`spec`, `prd + techspec`, `brief + techspec`, …). Newest first.\n\nCommit as `docs: add \u003Cslug> spec set` and push.\n\n*Done when:* every relative link in the README resolves and the commit is on `main`.\n\n## Step 4 — Write the issue body\n\nRead `.agents\u002Fskills\u002Fcy-issue-to-spec\u002Freferences\u002Fissue-body.md` in full and build the body against it.\n\n*Done when:* the body opens with the spec-set link block and every section of the skeleton is either written or deliberately absent.\n\n## Step 5 — Open the mirror\n\nCreate or update the GitHub issue: title matching the spec's subject, labels `roadmap` + `planned` (removing `needs-plan`), the Step 4 body, and a closing `Roadmap item tracked in Linear: [CY-NNN](…)` line.\n\nCreate or update the Linear issue with the same title and the same body, swapping the footer for `Tracked on GitHub: \u003Curl>`. Linear renders GitHub callout syntax as plain text — convert a `> [!NOTE]` block to a bold sentence.\n\nVerify with the audit helper (**read-only**):\n\n```bash\npython3 .agents\u002Fskills\u002Fcy-issue-to-spec\u002Fscripts\u002Fcheck-tracker-sync.py --linear-json \u003Cexport>\n```\n\nSave the Linear MCP `list_issues` result to a file first; without `--linear-json` the helper audits only the GitHub half.\n\n*Done when:* the helper exits 0 with no defects, and both issues carry a link to each other.\n\n## Reference\n\n- Publishing an already-archived spec skips Step 0 and Step 4's tracking link when no issue exists — the README row is then the only index entry.\n- Renaming a published folder breaks the links already sitting in both trackers; update the issue bodies in the same change.\n- `references\u002Fissue-body.md` — the issue-body skeleton and where each part comes from in the spec.\n- `scripts\u002Fpublish-spec.py` — **mutating**; stages, scrubs, scans, and link-checks a spec set.\n- `scripts\u002Fcheck-tracker-sync.py` — **read-only**; audits titles, states, and links across the mirror.\n",{"name":5,"description":7,"argument-hint":38,"disable-model-invocation":39},"[spec slug or issue number]",true,"main","65613632bb94072e27fc5015d17387e28a870111",".agents\u002Fskills\u002Fcy-issue-to-spec",187,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy","https:\u002F\u002Fcompozy.com","https:\u002F\u002Fgithub.com\u002Fcompozy","An OS for AI agents","2026-11-15 03:55:11",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":39},[51,54,57],{"tool":52,"command":53},"npx","npx skills add compozy\u002Fcompozy --skill cy-issue-to-spec",{"tool":55,"command":56},"bunx","bunx skills add compozy\u002Fcompozy --skill cy-issue-to-spec",{"tool":58,"command":59},"pnpm","pnpm dlx skills add compozy\u002Fcompozy --skill cy-issue-to-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcy-issue-to-spec\u002FSKILL.md",[62,68,74],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fissue-body.md","REFERENCE","参考文档",3371,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcy-issue-to-spec\u002Freferences\u002Fissue-body.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fcheck-tracker-sync.py","SCRIPT","脚本",3901,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcy-issue-to-spec\u002Fscripts\u002Fcheck-tracker-sync.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fpublish-spec.py",6440,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcy-issue-to-spec\u002Fscripts\u002Fpublish-spec.py",[79,115,140,162,173,185],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":33},"01M6MD7W312X49RNEJRKKVKTTD","security-review","Security code review for vulnerabilities. Use when asked to \"security review\", \"find vulnerabilities\", \"check for security issues\", \"audit security\", \"OWASP review\", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.","CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114],"security","security review","review","injection","authentication","code review","issues","Bash","code","xss","audit","systematic","read","reporting","cryptography","owasp","systematic review","for","use","task","when","audit security",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":126,"publishedAt":33},"01M6MD5K93G1GP8VA56V2FEPZV","lesson-learned","Extract evidence-backed engineering lessons from recent changes or incidents. Use for requested reflection, lesson updates, or retiring an obsolete workflow rule.","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flesson-learned\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[127,128,129,110,130,131,132,133,134,135,136,137,111,138,139],"learned","lesson learned","lesson","changes","evidence","incidents","workflow","engineering","updates","extract","rule","lessons","reflection",{"skillNo":141,"name":9,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":33},"01M6MDPNH3J60VRCGTPHVTHZR8","Operate CompozyOS. Use when working with CompozyOS sessions, agents, native tools, skills, tasks, Loops, Goals, Terminal, desktops and windows, automation, extensions, or configuration. Don't use for unrelated projects.","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fskills\u002Fcompozy\u002FSKILL.md",[],[9,146,147,148,149,110,150,31,111,151,152,153,154,155,156,157,158,159,160,161,113],"sessions","windows","projects","operate","runtime","automation","tasks","extensions","with","loops","unrelated","goals","native","terminal","configuration","Tools",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":33},"01M6MDPHKNPQHJ1TF21E1HSFNF","remotion-upgrade","Upgrade Remotion, and related packages","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fpackages\u002Flaunch-video\u002F.agents\u002Fskills\u002Fremotion-upgrade\u002FSKILL.md",[],[169,170,171,172],"remotion upgrade","upgrade","Remotion","packages",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":33},"01M6MDPFT91ZWC7Z09MRNZPAJG","remotion-studio","Preview a Remotion video","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fpackages\u002Flaunch-video\u002F.agents\u002Fskills\u002Fremotion-studio\u002FSKILL.md",[],[180,181,171,182,183,184],"studio","remotion studio","Video","preview","remotion video",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":33},"01M6MDPD5XDZPYB5NAZGKMPXWC","remotion-saas","Build an app with Remotion","https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fpackages\u002Flaunch-video\u002F.agents\u002Fskills\u002Fremotion-saas\u002FSKILL.md",[],[192,193,171,154,194,195],"saas","remotion saas","app","build"]