[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NYRY95B2FC2Y2EKBZS29B5":3,"skill-same:01M6NYRY95B2FC2Y2EKBZS29B5":64},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6NYRY95B2FC2Y2EKBZS29B5","brief-to-tasks",null,"Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions \"tasks\" or \"breakdown\".","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-software\u002Fjulianoczkowski\u002Fbrief-to-tasks\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"tasks","brief to tasks","brief","create","markdown","plan","create tasks","work","user","use","implementation","checklist","plan implementation","as","break down","break","design brief","down","design","2026-11-10 10:12:30",false,"---\nname: brief-to-tasks\ndescription: Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions \"tasks\" or \"breakdown\".\n---\n\nThis skill turns a design brief into an ordered, buildable task list. Each task is a vertical slice: a piece of UI that can be built, reviewed, and verified on its own.\n\n## Example prompts\n\n- \"Break the brief into tasks\"\n- \"What should I build first?\"\n- \"Create a task list from the design brief\"\n- \"Plan the build order for this feature\"\n\n## Process\n\n1. Read the design brief. Look for `.design\u002F*\u002FDESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. Also check for `INFORMATION_ARCHITECTURE.md` and a tokens file in the same subfolder. If none exist, ask the user to describe what they are building.\n\n2. Explore the existing codebase to understand what is already built. Scan specifically for:\n   - **Component directories**: `components\u002F`, `ui\u002F`, `shared\u002F` and list every component by name\n   - **Existing pages\u002Fviews**: what is already built that this feature must coexist with\n   - **Token\u002Ftheme files**: `tokens.css`, `globals.css`, Tailwind config, theme providers\n   - **File naming conventions**: kebab-case, PascalCase, how files are organized (by feature, by type)\n   - **Test files**: if tests exist alongside components, new tasks should include test expectations\n   - **Package.json dependencies**: what UI libraries, animation libraries, and icon sets are already installed\n   - Classify each relevant component as: will be reused as-is, needs modification, or does not exist yet. Only components that need modification or creation get their own tasks.\n\n3. Break the work into vertical slices. Each task should:\n   - Be independently buildable (no task should block another unless noted).\n   - Include structure, styling, and interaction in a single task (not \"build HTML\" then \"add CSS\" then \"add JS\" as separate tasks).\n   - Be verifiable: you can look at the result and confirm it matches the brief.\n   - Be small enough to complete in a single session.\n\n4. Order tasks by:\n   - **Dependencies first**: foundational elements (tokens, layout shells, shared components) before page-specific work.\n   - **Visual priority**: the most prominent UI element early, so the user can validate the aesthetic direction before investing in details.\n   - **Risk first**: the hardest or most uncertain piece early, so problems surface before everything else is built around them.\n\n5. Save the task list as `TASKS.md` in the same `.design\u002F\u003Cfeature-slug>\u002F` subfolder as the design brief.\n\n## Task List Template\n\n```markdown\n\n# Build Tasks: [Feature\u002FPage Name]\n\nGenerated from: .design\u002F\u003Cfeature-slug>\u002FDESIGN_BRIEF.md\nDate: [date]\n\n## Foundation\n- [ ] **[Task name]**: [One sentence describing what to build and what \"done\" looks like]. _Reuses: [existing components\u002Ftokens if any]._\n- [ ] **[Task name]**: [Description]. _New component._\n\n## Core UI\n- [ ] **[Task name]**: [Description]. _Depends on: [task name if any]._\n- [ ] **[Task name]**: [Description].\n\n## Interactions & States\n- [ ] **[Task name]**: [Description]. Covers: [list of states, e.g., hover, loading, error, empty].\n- [ ] **[Task name]**: [Description].\n\n## Responsive & Polish\n- [ ] **[Task name]**: [Description]. Breakpoints: [which ones].\n- [ ] **[Task name]**: Accessibility pass. [Specific checks from the brief].\n\n## Review\n- [ ] **Design review**: Run \u002Fdesign-review against the brief.\n```\n\n## Rules\n\n- Every task must reference whether it reuses, modifies, or creates components.\n- Never create a task that is only \"set up the project\" or \"create the file structure.\" Those are not vertical slices.\n- If the brief specifies an aesthetic philosophy, note it in the first build task so the visual direction is established immediately.\n- Group related tasks but do not nest them more than one level deep. Flat lists are easier to work through.\n","This skill turns a design brief into an ordered, buildable task list. Each task is a vertical slice: a piece of UI that can be built, reviewed, and verified on its own.\n\n## Example prompts\n\n- \"Break the brief into tasks\"\n- \"What should I build first?\"\n- \"Create a task list from the design brief\"\n- \"Plan the build order for this feature\"\n\n## Process\n\n1. Read the design brief. Look for `.design\u002F*\u002FDESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. Also check for `INFORMATION_ARCHITECTURE.md` and a tokens file in the same subfolder. If none exist, ask the user to describe what they are building.\n\n2. Explore the existing codebase to understand what is already built. Scan specifically for:\n   - **Component directories**: `components\u002F`, `ui\u002F`, `shared\u002F` and list every component by name\n   - **Existing pages\u002Fviews**: what is already built that this feature must coexist with\n   - **Token\u002Ftheme files**: `tokens.css`, `globals.css`, Tailwind config, theme providers\n   - **File naming conventions**: kebab-case, PascalCase, how files are organized (by feature, by type)\n   - **Test files**: if tests exist alongside components, new tasks should include test expectations\n   - **Package.json dependencies**: what UI libraries, animation libraries, and icon sets are already installed\n   - Classify each relevant component as: will be reused as-is, needs modification, or does not exist yet. Only components that need modification or creation get their own tasks.\n\n3. Break the work into vertical slices. Each task should:\n   - Be independently buildable (no task should block another unless noted).\n   - Include structure, styling, and interaction in a single task (not \"build HTML\" then \"add CSS\" then \"add JS\" as separate tasks).\n   - Be verifiable: you can look at the result and confirm it matches the brief.\n   - Be small enough to complete in a single session.\n\n4. Order tasks by:\n   - **Dependencies first**: foundational elements (tokens, layout shells, shared components) before page-specific work.\n   - **Visual priority**: the most prominent UI element early, so the user can validate the aesthetic direction before investing in details.\n   - **Risk first**: the hardest or most uncertain piece early, so problems surface before everything else is built around them.\n\n5. Save the task list as `TASKS.md` in the same `.design\u002F\u003Cfeature-slug>\u002F` subfolder as the design brief.\n\n## Task List Template\n\n```markdown\n\n# Build Tasks: [Feature\u002FPage Name]\n\nGenerated from: .design\u002F\u003Cfeature-slug>\u002FDESIGN_BRIEF.md\nDate: [date]\n\n## Foundation\n- [ ] **[Task name]**: [One sentence describing what to build and what \"done\" looks like]. _Reuses: [existing components\u002Ftokens if any]._\n- [ ] **[Task name]**: [Description]. _New component._\n\n## Core UI\n- [ ] **[Task name]**: [Description]. _Depends on: [task name if any]._\n- [ ] **[Task name]**: [Description].\n\n## Interactions & States\n- [ ] **[Task name]**: [Description]. Covers: [list of states, e.g., hover, loading, error, empty].\n- [ ] **[Task name]**: [Description].\n\n## Responsive & Polish\n- [ ] **[Task name]**: [Description]. Breakpoints: [which ones].\n- [ ] **[Task name]**: Accessibility pass. [Specific checks from the brief].\n\n## Review\n- [ ] **Design review**: Run \u002Fdesign-review against the brief.\n```\n\n## Rules\n\n- Every task must reference whether it reuses, modifies, or creates components.\n- Never create a task that is only \"set up the project\" or \"create the file structure.\" Those are not vertical slices.\n- If the brief specifies an aesthetic philosophy, note it in the first build task so the visual direction is established immediately.\n- Group related tasks but do not nest them more than one level deep. Flat lists are easier to work through.\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","plan-software\u002Fjulianoczkowski\u002Fbrief-to-tasks",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill brief-to-tasks",{"tool":56,"command":57},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill brief-to-tasks",{"tool":59,"command":60},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill brief-to-tasks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-software\u002Fjulianoczkowski\u002Fbrief-to-tasks\u002FSKILL.md",true,[],[65,101,115,135,156,180],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":81,"publishedAt":38},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[82,83,84,85,86,87,88,89,90,91,92,28,93,94,95,96,97,98,99,100],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[108,109,83,110,111,28,112,113,114],"crafting effective readmes","README","templates","type","project","guidance","files",{"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":124,"publishedAt":38},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000038","人力资源",[125,126,127,128,129,130,131,132,133,134,99],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":38},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[109,142,143,144,129,145,146,112,147,148,43,149,150,151,152,153,99,154,155],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":38},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[163,164,28,165,27,166,167,168,169,22,170,171,172,173,174,175,176,177,178,179],"ubiquitous language","language","extract","glossary","model","terms","ddd","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":188,"publishedAt":38},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[186,187],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[189,190,173,152,83,191,90,192,193,194,195,196,197,198,199,96,200,201,100,202],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]