[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D77ACVJNEQDX4KXESACGJ2":3,"skill-same:01M7D77ACVJNEQDX4KXESACGJ2":66},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7D77ACVJNEQDX4KXESACGJ2","enrich-work-item",null,"Enriches an existing Epic, Feature, User Story, or Task into the host team's structured format using type-specific enricher prompts (emoji sections, scope blocks, complexity drivers, ASCII diagrams). Use when the user runs \u002Fenrich-work-item, asks to \"enrich a ticket\", \"enrich this issue\", \"format this user story\", \"polish this feature\", \"structure this epic\", or provides a path, URL, or pasted text plus work-item type. For raw title + requirement bullets from scratch, use generate-work-item instead. For plain-language narrative inside enricher sections, this skill delegates a sub-pass to generate-plain-language-documentation after enricher assembly.","Monolith-INC\u002Fmonolithic-dev-harness","Monolith-INC","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235230192?v=4","01M75C94857P7W1N13N4K4E016","Monolith INC","01M7D737W93VBSP0P111E1AJ7M",1,"MIT","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: enrich-work-item\ndescription: >\n  Enriches an existing Epic, Feature, User Story, or Task into the host team's structured format using type-specific enricher prompts (emoji sections, scope blocks, complexity drivers, ASCII diagrams). Use when the user runs \u002Fenrich-work-item, asks to \"enrich a ticket\", \"enrich this issue\", \"format this user story\", \"polish this feature\", \"structure this epic\", or provides a path, URL, or pasted text plus work-item type. For raw title + requirement bullets from scratch, use generate-work-item instead. For plain-language narrative inside enricher sections, this skill delegates a sub-pass to generate-plain-language-documentation after enricher assembly.\nlicense: MIT\n---\n\n# Enrich Work Item\n\nConductor for applying the **enricher pattern** to an existing work-item description. Load references\nas each phase needs them.\n\nReferences (start at `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrich-work-item.md`):\n\n- `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrich-work-item.md` — type map, enricher routing, artifacts paths.\n- `..\u002F..\u002Fcommon\u002Ftemplates\u002Foutput-formats.md` — per-type output contracts.\n- `..\u002F..\u002Fcommon\u002Ftemplates\u002F` — **read-only shape contracts**. Validate enriched\n  output against the matching template before presenting.\n- `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrichers\u002F` — **authoritative** prose rules:\n  - `epic-enricher.prompt.md`, `feature-enricher.prompt.md`, `work-item-enricher.prompt.md`\n- `..\u002F..\u002Fcommon\u002Fspecs\u002Fenrich-work-item\u002F` — spec forms for optional analysis artifacts.\n- `.\u002Freferences\u002Fexamples\u002F` — illustrative dummy outputs (content reference only; shape contract is\n  `.\u002Freferences\u002Fcanonical\u002F`).\n- `..\u002F..\u002Freferences\u002Fdecomposition-rules.md` — hierarchy, story-point heuristic.\n- `..\u002F..\u002Freferences\u002Fticket-structure.md` — draft file constraints.\n- `..\u002F..\u002Fcommon\u002Fproviders.md` — neutral artifact contract and provider translations.\n- `..\u002Fgenerate-plain-language-documentation\u002Freferences\u002Fintegration-notes.md` — prose polish sub-pass\n  (PHASE 4).\n\n**Not in scope:** generating a raw work item from a title alone — use `generate-work-item` first.\n\n---\n\n## PHASE 0 — COLLECT INPUTS\n\nGather inputs **one at a time** via the host UI. Each step: brief purpose, required vs optional.\n\n| Input | Required | Purpose |\n| --- | --- | --- |\n| `source` | yes | `url` \\| local `path` \\| pasted `text` — the material to enrich |\n| `work_item_type` | yes | `epic` \\| `feature` \\| `user-story` \\| `task` |\n| `parent` | when type ≠ epic | Parent id or tracker link for hierarchy context |\n| `attachment` | no | Extra doc URL or path |\n\nAccept `\u002Fenrich-work-item` flags or conversational inference (see Examples).\n\nNormalize type → enricher + the tracker kind (`tracker_describe` `kinds`) per `pipeline.md`.\n\nEvery tracker read and write goes through the harness gateway (`tracker_*` tools); never call a\ntracker's own tools. Ask `harness document path` for every document's and draft's path\n(`..\u002F..\u002Freferences\u002Fdocument-layout.md`).\n\n---\n\n## PHASE 1 — INGEST\n\n1. Load `source`:\n   - **Tracker id or link** — read the id with the tracker's `ids` patterns (`tracker_describe`),\n     then `tracker_get_work_item`; read its artifacts with `tracker_list_artifacts`, parse the\n     description for linked docs\u002FURLs\u002Fpaths, and fetch that content into `supplementary_context`.\n     Set **Descrição Original** from the item's `description` verbatim.\n   - **path** — read local markdown; capture body verbatim.\n   - **url** (not a tracker link) — fetch external doc; capture description verbatim.\n   - **text** — treat pasted content as the description to enrich.\n2. If `parent` provided: `tracker_get_work_item` — capture parent chain for context and filename\n   prefix. When `source` is a tracker item and `parent` omitted, use its `parent_id`.\n3. If `attachment` provided: read or fetch; fold into enricher context (dedupe against tracker\n   artifacts already ingested).\n4. Preserve **Descrição Original** text exactly for the enricher output section.\n\n---\n\n## PHASE 2 — ROUTE ENRICHER\n\nRead the common output contract and matching enricher:\n\n| `work_item_type` | Enricher |\n| --- | --- |\n| `epic` | `enrichers\u002Fepic-enricher.prompt.md` |\n| `feature` | `enrichers\u002Ffeature-enricher.prompt.md` |\n| `user-story` | `enrichers\u002Fwork-item-enricher.prompt.md` |\n| `task` | `enrichers\u002Ftask-enricher.prompt.md` |\n\nLoad enricher prompts from `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrichers\u002F`.\n\nFollow enricher **Contexto Obrigatório** when host monorepo docs exist; skip gracefully when absent.\n\nFor user-story sources, classify Bug vs User Story per enricher §1 keywords when applicable.\n\n---\n\n## PHASE 3 — WRITE SPEC (optional artifacts path)\n\nWhen the item will be persisted, fill the matching common `spec-*.md` into the path\n`harness document path --type spec --item \u003Ckey>` prints (`--new` before the item exists). Skip when\nthe destination is chat-only.\n\n---\n\n## PHASE 4 — ENRICH\n\nApply the enricher rules to produce the **exact** output format defined in enricher §4 (Epic\u002FFeature) or\n§6 (work item). The enriched body IS the deliverable — emoji sections, scope blocks, complexity\ndrivers, ASCII diagrams as the enricher specifies.\n\n**Plain-language sub-pass:** Read\n`..\u002Fgenerate-plain-language-documentation\u002Freferences\u002Fintegration-notes.md` § enrich-work-item; polish\nnarrative paragraphs inside sections (not emoji headings; not **Descrição Original**). Glossary-verify\nwhen locale is pt-BR.\n\nRun the enricher **Checklist de Auto-Revisão** before presenting.\n\nCompare shape against `..\u002F..\u002Fcommon\u002Ftemplates\u002Fcanonical-\u003Ctype>.md` (read-only contract; do not\nedit). Use `.\u002Freferences\u002Fexamples\u002Fexample-\u003Ctype>.md` only for illustrative content patterns.\n\nPresent the enriched markdown in chat. Suggest a title outside the markdown block when the enricher\nrequires it (work-item enricher).\n\n---\n\n## PHASE 5 — GATE & DESTINATION\n\n**── GATE —** Write the enriched body as a draft ticket (`harness document path --type ticket`,\nin `Tickets\u002FReady\u002F`), show it with `harness workflow show --artifact \u003Cdraft>`, then ask\n`harness decision present --gate publish-items` with the draft as `--artifact`. Silence is not\napproval.\n\nThe destination is the selected tracker. Write nothing anywhere else unless the user asks for\nchat-only output.\n\n---\n\n## PHASE 6 — PERSIST\n\nWrite through the gateway per `..\u002F..\u002Fcommon\u002Fproviders.md`: an existing item with\n`tracker_update_work_item` (`description` — the approved draft's body, word for word — and `title`\nwhen it changed), a new item with `tracker_create_work_item`. With the local tracker, creating the\nitem turns its draft into the tracked ticket. Artifacts use only `provider`, string `provider_id`,\nand string `parent_id`.\n\n---\n\n## PHASE 7 — VERIFY\n\nRead the item back with `tracker_get_work_item` and verify its parent and description. Update the draft's neutral\nprovider identity fields when creating new items.\n\nOn failure: STOP and report.\n\nAppend checkpoint to open `Agent_Sessions\u002F` record when the host keeps a session artifacts path.\n\n---\n\n## Operating rules\n\n- **Enricher is authoritative** — output matches enricher § output format, not generate-work-item's\n  uniform three-part layout.\n- **Verbatim original** — always include Descrição Original from ingest (work-item description only;\n  attachment text feeds enrichment context, not Descrição Original).\n- **WHAT not HOW** — per enricher quality rules.\n- **One gate** before persistence writes.\n- **Locale** — Português BR for host-team enrichers unless the source is clearly another language.\n\n## Examples\n\n**Slash command:**\n\n```\n\u002Fenrich-work-item --type feature --source Tickets\u002FReady\u002F6800-oauth-login.md --parent 6800\n```\n\n**Conversational trigger:**\n\n> Enrich this user story — [pasted description]\n\n→ Infer `work_item_type: user-story`, `source: text`, run enricher pipeline.\n\n**Tracker source:**\n\n> Format issue 6871 in the team template\n\n→ `source: url` (tracker item), read it with `tracker_get_work_item` (work item + artifacts +\ndescription refs), enrich, present for approval.\n","# Enrich Work Item\n\nConductor for applying the **enricher pattern** to an existing work-item description. Load references\nas each phase needs them.\n\nReferences (start at `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrich-work-item.md`):\n\n- `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrich-work-item.md` — type map, enricher routing, artifacts paths.\n- `..\u002F..\u002Fcommon\u002Ftemplates\u002Foutput-formats.md` — per-type output contracts.\n- `..\u002F..\u002Fcommon\u002Ftemplates\u002F` — **read-only shape contracts**. Validate enriched\n  output against the matching template before presenting.\n- `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrichers\u002F` — **authoritative** prose rules:\n  - `epic-enricher.prompt.md`, `feature-enricher.prompt.md`, `work-item-enricher.prompt.md`\n- `..\u002F..\u002Fcommon\u002Fspecs\u002Fenrich-work-item\u002F` — spec forms for optional analysis artifacts.\n- `.\u002Freferences\u002Fexamples\u002F` — illustrative dummy outputs (content reference only; shape contract is\n  `.\u002Freferences\u002Fcanonical\u002F`).\n- `..\u002F..\u002Freferences\u002Fdecomposition-rules.md` — hierarchy, story-point heuristic.\n- `..\u002F..\u002Freferences\u002Fticket-structure.md` — draft file constraints.\n- `..\u002F..\u002Fcommon\u002Fproviders.md` — neutral artifact contract and provider translations.\n- `..\u002Fgenerate-plain-language-documentation\u002Freferences\u002Fintegration-notes.md` — prose polish sub-pass\n  (PHASE 4).\n\n**Not in scope:** generating a raw work item from a title alone — use `generate-work-item` first.\n\n---\n\n## PHASE 0 — COLLECT INPUTS\n\nGather inputs **one at a time** via the host UI. Each step: brief purpose, required vs optional.\n\n| Input | Required | Purpose |\n| --- | --- | --- |\n| `source` | yes | `url` \\| local `path` \\| pasted `text` — the material to enrich |\n| `work_item_type` | yes | `epic` \\| `feature` \\| `user-story` \\| `task` |\n| `parent` | when type ≠ epic | Parent id or tracker link for hierarchy context |\n| `attachment` | no | Extra doc URL or path |\n\nAccept `\u002Fenrich-work-item` flags or conversational inference (see Examples).\n\nNormalize type → enricher + the tracker kind (`tracker_describe` `kinds`) per `pipeline.md`.\n\nEvery tracker read and write goes through the harness gateway (`tracker_*` tools); never call a\ntracker's own tools. Ask `harness document path` for every document's and draft's path\n(`..\u002F..\u002Freferences\u002Fdocument-layout.md`).\n\n---\n\n## PHASE 1 — INGEST\n\n1. Load `source`:\n   - **Tracker id or link** — read the id with the tracker's `ids` patterns (`tracker_describe`),\n     then `tracker_get_work_item`; read its artifacts with `tracker_list_artifacts`, parse the\n     description for linked docs\u002FURLs\u002Fpaths, and fetch that content into `supplementary_context`.\n     Set **Descrição Original** from the item's `description` verbatim.\n   - **path** — read local markdown; capture body verbatim.\n   - **url** (not a tracker link) — fetch external doc; capture description verbatim.\n   - **text** — treat pasted content as the description to enrich.\n2. If `parent` provided: `tracker_get_work_item` — capture parent chain for context and filename\n   prefix. When `source` is a tracker item and `parent` omitted, use its `parent_id`.\n3. If `attachment` provided: read or fetch; fold into enricher context (dedupe against tracker\n   artifacts already ingested).\n4. Preserve **Descrição Original** text exactly for the enricher output section.\n\n---\n\n## PHASE 2 — ROUTE ENRICHER\n\nRead the common output contract and matching enricher:\n\n| `work_item_type` | Enricher |\n| --- | --- |\n| `epic` | `enrichers\u002Fepic-enricher.prompt.md` |\n| `feature` | `enrichers\u002Ffeature-enricher.prompt.md` |\n| `user-story` | `enrichers\u002Fwork-item-enricher.prompt.md` |\n| `task` | `enrichers\u002Ftask-enricher.prompt.md` |\n\nLoad enricher prompts from `..\u002F..\u002Fcommon\u002Fworkflows\u002Fenrichers\u002F`.\n\nFollow enricher **Contexto Obrigatório** when host monorepo docs exist; skip gracefully when absent.\n\nFor user-story sources, classify Bug vs User Story per enricher §1 keywords when applicable.\n\n---\n\n## PHASE 3 — WRITE SPEC (optional artifacts path)\n\nWhen the item will be persisted, fill the matching common `spec-*.md` into the path\n`harness document path --type spec --item \u003Ckey>` prints (`--new` before the item exists). Skip when\nthe destination is chat-only.\n\n---\n\n## PHASE 4 — ENRICH\n\nApply the enricher rules to produce the **exact** output format defined in enricher §4 (Epic\u002FFeature) or\n§6 (work item). The enriched body IS the deliverable — emoji sections, scope blocks, complexity\ndrivers, ASCII diagrams as the enricher specifies.\n\n**Plain-language sub-pass:** Read\n`..\u002Fgenerate-plain-language-documentation\u002Freferences\u002Fintegration-notes.md` § enrich-work-item; polish\nnarrative paragraphs inside sections (not emoji headings; not **Descrição Original**). Glossary-verify\nwhen locale is pt-BR.\n\nRun the enricher **Checklist de Auto-Revisão** before presenting.\n\nCompare shape against `..\u002F..\u002Fcommon\u002Ftemplates\u002Fcanonical-\u003Ctype>.md` (read-only contract; do not\nedit). Use `.\u002Freferences\u002Fexamples\u002Fexample-\u003Ctype>.md` only for illustrative content patterns.\n\nPresent the enriched markdown in chat. Suggest a title outside the markdown block when the enricher\nrequires it (work-item enricher).\n\n---\n\n## PHASE 5 — GATE & DESTINATION\n\n**── GATE —** Write the enriched body as a draft ticket (`harness document path --type ticket`,\nin `Tickets\u002FReady\u002F`), show it with `harness workflow show --artifact \u003Cdraft>`, then ask\n`harness decision present --gate publish-items` with the draft as `--artifact`. Silence is not\napproval.\n\nThe destination is the selected tracker. Write nothing anywhere else unless the user asks for\nchat-only output.\n\n---\n\n## PHASE 6 — PERSIST\n\nWrite through the gateway per `..\u002F..\u002Fcommon\u002Fproviders.md`: an existing item with\n`tracker_update_work_item` (`description` — the approved draft's body, word for word — and `title`\nwhen it changed), a new item with `tracker_create_work_item`. With the local tracker, creating the\nitem turns its draft into the tracked ticket. Artifacts use only `provider`, string `provider_id`,\nand string `parent_id`.\n\n---\n\n## PHASE 7 — VERIFY\n\nRead the item back with `tracker_get_work_item` and verify its parent and description. Update the draft's neutral\nprovider identity fields when creating new items.\n\nOn failure: STOP and report.\n\nAppend checkpoint to open `Agent_Sessions\u002F` record when the host keeps a session artifacts path.\n\n---\n\n## Operating rules\n\n- **Enricher is authoritative** — output matches enricher § output format, not generate-work-item's\n  uniform three-part layout.\n- **Verbatim original** — always include Descrição Original from ingest (work-item description only;\n  attachment text feeds enrichment context, not Descrição Original).\n- **WHAT not HOW** — per enricher quality rules.\n- **One gate** before persistence writes.\n- **Locale** — Português BR for host-team enrichers unless the source is clearly another language.\n\n## Examples\n\n**Slash command:**\n\n```\n\u002Fenrich-work-item --type feature --source Tickets\u002FReady\u002F6800-oauth-login.md --parent 6800\n```\n\n**Conversational trigger:**\n\n> Enrich this user story — [pasted description]\n\n→ Infer `work_item_type: user-story`, `source: text`, run enricher pipeline.\n\n**Tracker source:**\n\n> Format issue 6871 in the team template\n\n→ `source: url` (tracker item), read it with `tracker_get_work_item` (work item + artifacts +\ndescription refs), enrich, present for approval.\n",{"name":5,"license":15,"description":24},"Enriches an existing Epic, Feature, User Story, or Task into the host team's structured format using type-specific enricher prompts (emoji sections, scope blocks, complexity drivers, ASCII diagrams). Use when the user runs \u002Fenrich-work-item, asks to \"enrich a ticket\", \"enrich this issue\", \"format this user story\", \"polish this feature\", \"structure this epic\", or provides a path, URL, or pasted text plus work-item type. For raw title + requirement bullets from scratch, use generate-work-item instead. For plain-language narrative inside enricher sections, this skill delegates a sub-pass to generate-plain-language-documentation after enricher assembly.\n","main","beda2ad5b6cc4caf3b0f62bc488106ae1d319f8e","plugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item",0,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness","https:\u002F\u002Fmonolithic-dev-harness.balmyangel65.chatgpt.site\u002F","https:\u002F\u002Fgithub.com\u002FMonolith-INC","Agentical Monolithics Cognitivity","2026-11-14 19:32:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Monolith-INC\u002Fmonolithic-dev-harness --skill enrich-work-item",{"tool":40,"command":41},"bunx","bunx skills add Monolith-INC\u002Fmonolithic-dev-harness --skill enrich-work-item",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Monolith-INC\u002Fmonolithic-dev-harness --skill enrich-work-item","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item\u002FSKILL.md",true,[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"manifest.json","REFERENCE","参考文档",1463,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item\u002Fmanifest.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fexamples\u002Fexample-epic.md",1404,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item\u002Freferences\u002Fexamples\u002Fexample-epic.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fexamples\u002Fexample-feature.md",1092,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item\u002Freferences\u002Fexamples\u002Fexample-feature.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fexamples\u002Fexample-user-story.md",1198,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fenrich-work-item\u002Freferences\u002Fexamples\u002Fexample-user-story.md",[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D7D832ZX48F36GB1F76PST","validate-artifact","Validate a single agile artifact (Epic, Feature, User Story, or Task) against the toolkit rule set. Use when the user asks to \"validate this story\u002Ffeature\u002Fepic\", \"check this ticket\", \"is this artifact ready?\", or provides a local draft path or provider item and wants a quality report. Accepts a local draft or a tracker work item. Runs all checks non-blocking and emits a terminal report + persisted report. One artifact per invocation.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fvalidate-artifact\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D7C4SS2NP2RPWVV1MCKV1P","split-story","Lateral story-sizing skill. Takes a single User Story and determines if it should be split, how many sub-stories to create, and what split pattern to use — then drafts sub-stories and hands them off. Use when the user asks \"split this story\", \"is this story too big?\", \"analyze this story for sizing\", or provides an artifacts path \u002F tracker id \u002F file path \u002F raw text and wants a split recommendation. One story per invocation.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fsplit-story\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D7ACZA52N346HGSMMJZNB4","research-decision","Research a product, market, domain, competitor, user, or technical question in service of a named decision, producing a cited decision brief. Use when planning depends on current evidence rather than more ideation.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fresearch-decision\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D7A1TWTKH944PBW4TZAN8B","product-spec","Distill an idea, brief, PRD, UX contract, architecture spine, issue, or mixed notes into a compact canonical product contract with stable capabilities and companions. Use before backlog decomposition when intent is defined; update or validate an existing product spec through the same skill.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fproduct-spec\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7D79VZH4BJPBF85MBG0W5T4","product-requirements","Create, update, or validate a right-sized Product Requirements Document with stable requirements, explicit scope, user journeys where useful, and measurable outcomes. Use for multi-person or multi-epic alignment; skip it when a concise product spec is enough.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fproduct-requirements\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7D79QNTG9953KQCM4QZ6QSM","product-brief","Create, update, or validate a concise product brief that captures a clear concept, its users, value, scope, and success criteria. Use when the user wants a one- or two-page product narrative before a PRD or product spec.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fproduct-brief\u002FSKILL.md",[],[]]