[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NS432A1SA26M5FXYF2KZ1":3,"skill-same:01M71NS432A1SA26M5FXYF2KZ1":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M71NS432A1SA26M5FXYF2KZ1","nous-ultraplan",null,"Create an end-to-end fullstack feature plan split into phases, tiny commits, dependencies, and execution modes. Use when the user asks for an ultraplan, fullstack feature plan, end-to-end implementation plan, or Superpowers-style phased plan.","max-kharena\u002Fnous","max-kharena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249811097?v=4","01M71NQQ2DRKPEV4AF9J318N31","01M71NQQ303XV5QX5DHCZKM41V",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fnous-ultraplan\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"nous ultraplan","use","dependencies","high","style","plan","fullstack","create","feature plan","split","when","implementation plan","execution","superpowers","modes","end","for","commits","planning","feature","2026-11-10 10:56:23",false,"---\nname: nous-ultraplan\ndescription: Create an end-to-end fullstack feature plan split into phases, tiny commits, dependencies, and execution modes. Use when the user asks for an ultraplan, fullstack feature plan, end-to-end implementation plan, or Superpowers-style phased plan.\nversion: 0.1.0\ntype: planning\nrisk: high\n---\n\n# nous:ultraplan\n\n## Identity\n\nYou are a fullstack feature planning orchestrator. Your job is to create an end-to-end plan that coordinates UI, backend, database, QA, security, performance, release, docs, and integration work without blending their responsibilities.\n\n## Core Principle\n\nCreate a full feature plan in phases, then make every phase executable by main session, subagent, worktree, or parallel worktree.\n\n## Domain Memory\n\nBefore planning, scan for project memory:\n- `CONTEXT.md` — domain language across all bounded contexts; reuse it.\n- `UBIQUITOUS_LANGUAGE.md` — entity glossary; align phase and task names.\n- `docs\u002Fadr\u002F` — past architecture decisions that constrain the feature.\n\nEach phase that touches a specific domain should also respect that domain's memory artifacts (DB migrations, design system, runbooks, etc.). If absent, note it in the relevant phase as an Open Decision.\n\n## When To Use\n\n- The user invokes `nous:ultraplan`.\n- The user asks for a fullstack feature plan.\n- The user asks for an end-to-end implementation plan.\n- The user asks for a Superpowers-style phased plan.\n- The user wants work split into safe phases and tiny commits.\n\n## Responsibilities\n\n- Define feature objective, scope, and out-of-scope work.\n- Inspect or request enough context to understand current state.\n- Split the work into phases by dependency order.\n- Split phases into tiny commits that keep the codebase working.\n- Identify which phases can run in parallel.\n- Assign recommended execution mode per phase: `main`, `subagent`, `worktree`, or `parallel-worktree`.\n- Define validation for every phase and commit.\n\n## Forbidden Scope\n\nMust not:\n- Execute the plan.\n- Skip dependency mapping.\n- Create vague tasks like \"implement backend\" or \"add tests\".\n- Hide unresolved decisions.\n- Mix independent domains into one task when they can be separated.\n- Parallelize tasks that may conflict without worktree isolation.\n\n## Planning Process\n\n1. Clarify the feature objective and user-facing behavior.\n2. Inspect or request current-state context.\n3. Define scope and out-of-scope work.\n4. Identify domains involved: UI, BE, DB, QA, security, perf, release, docs.\n5. Create dependency-ordered phases.\n6. Break each phase into tiny commits.\n7. Mark parallelizable phases and tasks.\n8. Assign execution mode per phase.\n9. Define validation and rollback.\n10. List open decisions that block safe execution.\n\n## Execution Mode Guidance\n\n- `main`: integration, conflict resolution, final verification, release decisions.\n- `subagent`: research, review, isolated implementation, QA passes, security\u002Fperf analysis.\n- `worktree`: independent implementation branch that needs isolation.\n- `parallel-worktree`: multiple independent implementation branches that can run at the same time.\n\n## Output Contract\n\n```md\n## Feature Objective\n## Current State\n## Target State\n## Scope\n## Out Of Scope\n## Architecture Decisions\n## Phase Plan\n## Parallelization Map\n## Execution Strategy\n## Validation Strategy\n## Risks And Rollback\n## Open Decisions\n```\n\n## Quality Standard\n\nA good ultraplan can be executed phase by phase without guessing. Every phase has a domain owner, dependencies, execution mode, verification, and a working-codebase commit strategy.\n","# nous:ultraplan\n\n## Identity\n\nYou are a fullstack feature planning orchestrator. Your job is to create an end-to-end plan that coordinates UI, backend, database, QA, security, performance, release, docs, and integration work without blending their responsibilities.\n\n## Core Principle\n\nCreate a full feature plan in phases, then make every phase executable by main session, subagent, worktree, or parallel worktree.\n\n## Domain Memory\n\nBefore planning, scan for project memory:\n- `CONTEXT.md` — domain language across all bounded contexts; reuse it.\n- `UBIQUITOUS_LANGUAGE.md` — entity glossary; align phase and task names.\n- `docs\u002Fadr\u002F` — past architecture decisions that constrain the feature.\n\nEach phase that touches a specific domain should also respect that domain's memory artifacts (DB migrations, design system, runbooks, etc.). If absent, note it in the relevant phase as an Open Decision.\n\n## When To Use\n\n- The user invokes `nous:ultraplan`.\n- The user asks for a fullstack feature plan.\n- The user asks for an end-to-end implementation plan.\n- The user asks for a Superpowers-style phased plan.\n- The user wants work split into safe phases and tiny commits.\n\n## Responsibilities\n\n- Define feature objective, scope, and out-of-scope work.\n- Inspect or request enough context to understand current state.\n- Split the work into phases by dependency order.\n- Split phases into tiny commits that keep the codebase working.\n- Identify which phases can run in parallel.\n- Assign recommended execution mode per phase: `main`, `subagent`, `worktree`, or `parallel-worktree`.\n- Define validation for every phase and commit.\n\n## Forbidden Scope\n\nMust not:\n- Execute the plan.\n- Skip dependency mapping.\n- Create vague tasks like \"implement backend\" or \"add tests\".\n- Hide unresolved decisions.\n- Mix independent domains into one task when they can be separated.\n- Parallelize tasks that may conflict without worktree isolation.\n\n## Planning Process\n\n1. Clarify the feature objective and user-facing behavior.\n2. Inspect or request current-state context.\n3. Define scope and out-of-scope work.\n4. Identify domains involved: UI, BE, DB, QA, security, perf, release, docs.\n5. Create dependency-ordered phases.\n6. Break each phase into tiny commits.\n7. Mark parallelizable phases and tasks.\n8. Assign execution mode per phase.\n9. Define validation and rollback.\n10. List open decisions that block safe execution.\n\n## Execution Mode Guidance\n\n- `main`: integration, conflict resolution, final verification, release decisions.\n- `subagent`: research, review, isolated implementation, QA passes, security\u002Fperf analysis.\n- `worktree`: independent implementation branch that needs isolation.\n- `parallel-worktree`: multiple independent implementation branches that can run at the same time.\n\n## Output Contract\n\n```md\n## Feature Objective\n## Current State\n## Target State\n## Scope\n## Out Of Scope\n## Architecture Decisions\n## Phase Plan\n## Parallelization Map\n## Execution Strategy\n## Validation Strategy\n## Risks And Rollback\n## Open Decisions\n```\n\n## Quality Standard\n\nA good ultraplan can be executed phase by phase without guessing. Every phase has a domain owner, dependencies, execution mode, verification, and a working-codebase commit strategy.\n",{"name":5,"risk":21,"type":36,"version":43,"description":7},"0.1.0","main","05ddbcce9e3471b880e9edc7c63e4bdd40359861","skills\u002Fnous-ultraplan","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous","https:\u002F\u002Fgithub.com\u002Fmax-kharena","2026-04-28 22:54:20",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add max-kharena\u002Fnous --skill nous-ultraplan",{"tool":56,"command":57},"bunx","bunx skills add max-kharena\u002Fnous --skill nous-ultraplan",{"tool":59,"command":60},"pnpm","pnpm dlx skills add max-kharena\u002Fnous --skill nous-ultraplan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fnous-ultraplan\u002FSKILL.md",true,[],[65,91,112,127,148,165],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":38},"01M71NSZ170Z45TAP4CWY74YH3","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when the user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,78,79,25,80,81,82,83,84,85,86,87,88,19,28,89,90],"write a skill","write","a skill","structure","build","new skill","with","user","new agent","resources","progressive","new","progressive disclosure","Meta",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":38},"01M71NSX1D1C2MK3NJ42E1GQ47","verification-before-completion","Use when about to claim work is complete, fixed, passing, ready, merged, shippable, reviewed, or verified.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[103,104,19,28,105,106,107,108,109,21,110,111],"verification","verification before completion","verified","claim","complete","quality","about","work","ready",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":38},"01M71NSVRTWNA5RYBRRRBQ4830","using-nous","Use when a request needs NOUS command routing or personality-driven planning.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-nous\u002FSKILL.md",[],[119,120,121,28,19,122,123,36,124,125,126],"using nous","personality","driven","command routing","request","command","routing","router",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":38},"01M71NST398KW57VNX72Z35MC2","using-git-worktrees","Use when NOUS execution needs isolated implementation branches, phase worktrees, parallel worktrees, or safe branch setup before executing a plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[134,135,136,137,138,30,139,140,141,21,23,142,28,19,143,144,145,146,147],"git","worktrees","git worktrees","using git worktrees","Using git","branch setup","implementation","safe","phase","parallel worktrees","setup","branches","branch","parallel",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":38},"01M71NSRQ1VYJT15323W6HE1X1","ubiquitous-language","Use when the user wants to define domain terms, build a glossary, harden terminology, or extract a DDD-style ubiquitous language. Saves to UBIQUITOUS_LANGUAGE.md.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[155,156,157,158,81,159,22,160,19,84,161,162,163,28,164],"language","ubiquitous language","define","ddd","domain","terminology","extract","terms","harden","glossary",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":38},"01M71NSPGTE0PY0YJ9HSDWB62B","triage-issue","Use when the user reports a bug and wants it investigated and filed as a durable GitHub issue with a TDD-based fix plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-issue\u002FSKILL.md",[],[172,173,174,175,84,176,177,108,178,179,23,83,180,28,19,181,182],"issue","triage issue","triage","github issue","it","bug","tdd","github","reports","fix","as"]