[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NSVRTWNA5RYBRRRBQ4830":3,"skill-same:01M71NSVRTWNA5RYBRRRBQ4830":56},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M71NSVRTWNA5RYBRRRBQ4830","using-nous",null,"Use when a request needs NOUS command routing or personality-driven planning.","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\u002Fusing-nous\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28],"using nous","router","routing","command","planning","request","command routing","use","personality","when","driven","2026-11-10 10:56:23",false,"---\nname: using-nous\ndescription: Use when a request needs NOUS command routing or personality-driven planning.\nversion: 0.1.0\ntype: router\nrisk: low\n---\n\n# Using NOUS\n\n## Core Principle\n\nRoute first, then load exactly one planning personality.\n\n## When To Use\n\n- The user invokes `nous:*`.\n- The user asks for a plan from a domain specialist.\n- The user asks for UI, ultra UI, database, backend, QA, CEO\u002Fproduct, security, performance, release\u002Fdeploy\u002Finfra planning, an ultraplan, plan execution, quick execution, TDD, debugging, code review, branch finishing, parallel agents, verification, or workflow resource ingestion.\n- The user asks for a natural-language plan that maps cleanly to one NOUS planner.\n\n## When Not To Use\n\n- The user asks a simple factual question.\n- The user asks you to directly implement a small change and no specialist plan is needed.\n- The request is pure conversation.\n\n## Router Order\n\n1. Check explicit commands first in `core\u002Frouter\u002Ftriggers.json`, including planners, execution commands, verification, TDD, debugging, code review, branch finishing, parallel agents, `nous:write-skill`, and `nous:ingest-workflow-resource`.\n2. If no command is present, match natural-language triggers from `core\u002Frouter\u002Ftriggers.json`.\n3. If exactly one planner matches, load only that planner.\n4. If multiple planners match, ask one short clarification question.\n5. If no planner matches, say NOUS is not needed and continue normally.\n\n## HARD-GATE: Single Active Personality\n\nDo not blend planner personalities unless the user explicitly asks for a multi-role review.\n\n`write-a-skill`, `ingest-workflow-resource`, and `nous-execute-plan` are meta-skills, not planner personalities. They must still avoid loading unrelated planner personalities unless the task explicitly needs them.\n\n## Execution Routing Rule\n\nIf routing to `nous-execute-plan`, the executor must check for an existing plan before doing any implementation. If no plan exists, it must stop and propose the correct planning command.\n\nForbidden rationalizations:\n- \"A complete plan should include everything.\"\n- \"The adjacent concern is probably useful.\"\n- \"The implementation needs all domains anyway.\"\n\n## Planning Contract\n\nEvery planner must use this output shape:\n\n```md\n## Objective\n## Domain Analysis\n## Specialized Tasks\n## Dependencies\n## Risks\n## Validation Requirements\n## Success Metrics\n## Not In Scope\n```\n\n## Inline Self-Review\n\nBefore returning a plan, check:\n- Did I load only one planner?\n- Did I avoid adjacent-domain tasks?\n- Did I include `Not In Scope`?\n- Did I mark unknowns instead of inventing facts?\n- Did I keep the plan domain-specific rather than generic?\n\n## Output Contract\n\nIf routing succeeds, respond with the selected planner's plan. If ambiguous, ask one clarification question with the likely planners.\n","# Using NOUS\n\n## Core Principle\n\nRoute first, then load exactly one planning personality.\n\n## When To Use\n\n- The user invokes `nous:*`.\n- The user asks for a plan from a domain specialist.\n- The user asks for UI, ultra UI, database, backend, QA, CEO\u002Fproduct, security, performance, release\u002Fdeploy\u002Finfra planning, an ultraplan, plan execution, quick execution, TDD, debugging, code review, branch finishing, parallel agents, verification, or workflow resource ingestion.\n- The user asks for a natural-language plan that maps cleanly to one NOUS planner.\n\n## When Not To Use\n\n- The user asks a simple factual question.\n- The user asks you to directly implement a small change and no specialist plan is needed.\n- The request is pure conversation.\n\n## Router Order\n\n1. Check explicit commands first in `core\u002Frouter\u002Ftriggers.json`, including planners, execution commands, verification, TDD, debugging, code review, branch finishing, parallel agents, `nous:write-skill`, and `nous:ingest-workflow-resource`.\n2. If no command is present, match natural-language triggers from `core\u002Frouter\u002Ftriggers.json`.\n3. If exactly one planner matches, load only that planner.\n4. If multiple planners match, ask one short clarification question.\n5. If no planner matches, say NOUS is not needed and continue normally.\n\n## HARD-GATE: Single Active Personality\n\nDo not blend planner personalities unless the user explicitly asks for a multi-role review.\n\n`write-a-skill`, `ingest-workflow-resource`, and `nous-execute-plan` are meta-skills, not planner personalities. They must still avoid loading unrelated planner personalities unless the task explicitly needs them.\n\n## Execution Routing Rule\n\nIf routing to `nous-execute-plan`, the executor must check for an existing plan before doing any implementation. If no plan exists, it must stop and propose the correct planning command.\n\nForbidden rationalizations:\n- \"A complete plan should include everything.\"\n- \"The adjacent concern is probably useful.\"\n- \"The implementation needs all domains anyway.\"\n\n## Planning Contract\n\nEvery planner must use this output shape:\n\n```md\n## Objective\n## Domain Analysis\n## Specialized Tasks\n## Dependencies\n## Risks\n## Validation Requirements\n## Success Metrics\n## Not In Scope\n```\n\n## Inline Self-Review\n\nBefore returning a plan, check:\n- Did I load only one planner?\n- Did I avoid adjacent-domain tasks?\n- Did I include `Not In Scope`?\n- Did I mark unknowns instead of inventing facts?\n- Did I keep the plan domain-specific rather than generic?\n\n## Output Contract\n\nIf routing succeeds, respond with the selected planner's plan. If ambiguous, ask one clarification question with the likely planners.\n",{"name":5,"risk":34,"type":19,"version":35,"description":7},"low","0.1.0","main","05ddbcce9e3471b880e9edc7c63e4bdd40359861","skills\u002Fusing-nous","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous","https:\u002F\u002Fgithub.com\u002Fmax-kharena","2026-04-28 22:54:20",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add max-kharena\u002Fnous --skill using-nous",{"tool":48,"command":49},"bunx","bunx skills add max-kharena\u002Fnous --skill using-nous",{"tool":51,"command":52},"pnpm","pnpm dlx skills add max-kharena\u002Fnous --skill using-nous","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-nous\u002FSKILL.md",true,[],[57,84,106,129,147,165],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":68,"publishedAt":29},"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",[63],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[69,70,71,72,73,74,75,76,77,78,79,27,25,80,81,82,83],"a skill","write","write a skill","new","user","new skill","build","structure","create","with","progressive disclosure","progressive","Meta","new agent","resources",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":95,"publishedAt":29},"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",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[96,97,98,99,100,101,102,103,104,105,27,25],"verification before completion","verification","complete","verified","quality","about","high","work","ready","claim",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":29},"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",[],[113,114,115,116,117,118,119,120,121,102,122,123,27,25,124,125,126,127,128],"git","worktrees","git worktrees","using git worktrees","Using git","setup","branch setup","implementation","safe","plan","phase","parallel worktrees","execution","branch","parallel","branches",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":29},"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",[],[136,137,138,139,140,73,141,142,27,143,25,144,145,75,146],"language","ubiquitous language","terminology","style","terms","extract","harden","glossary","define","ddd","domain",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":29},"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",[],[154,155,156,157,73,158,159,100,160,161,122,78,162,27,25,163,164],"triage","issue","triage issue","github","it","bug","github issue","tdd","reports","fix","as",{"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":174,"publishedAt":29},"01M71NSN59ZV9BVTKYF8QZCZ7R","to-prd","Use when the user wants to turn the current conversation context into a PRD and submit it as a GitHub issue. No interview — synthesizes what has already been discussed.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fto-prd\u002FSKILL.md",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000031","产品经理",[175,176,164,157,177,178,27,158,73,179,22,180,160,155,25],"prd","to prd","conversation","interview","context","submit"]