[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4ZDN09CBE7XDTWFJ49GQB":3,"skill-same:01M6C4ZDN09CBE7XDTWFJ49GQB":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M6C4ZDN09CBE7XDTWFJ49GQB","awa-requirements",null,"Create or update requirements documents. Use this when asked to create, update or modify requirements.","ncoderz\u002Fawa","ncoderz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F124541034?v=4","01M6C4PHT3RMHEY3TK3TJKYX5F","01M6C4PHXT7RAP268HGXCRF8QA",1,"BSD-3-Clause","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-requirements\u002FSKILL.md",[],[18,19,20,21,22],"awa requirements","documents","create","update","use","2026-11-10 10:12:30",false,"---\nname: awa-requirements\ndescription: Create or update requirements documents. Use this when asked to create, update or modify requirements.\n---\n\n# Create or Update Requirements\n\n## Bootstrap\n\n\u003Ctool name=\"read_file\">\n \u003Cread path=\".awa\u002F.agent\u002Fawa.core.md\" required=\"true\" error=\"on not found\" \u002F>\n \u003Cread path=\".awa\u002Frules\u002F*.md\" required=\"true\" \u002F>\n \u003Cread path=\".awa\u002Fspecs\u002FARCHITECTURE.md\" required=\"true\" error=\"on not found\" \u002F>\n \u003Cread path=\".awa\u002F.agent\u002Fschemas\u002FREQ.schema.yaml\" required=\"true\" error=\"on not found\" \u002F>\n\u003C\u002Ftool>\n\n## User Input\n\n```text\n${input}\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Inputs\n\n\u003Cfile type=\"architecture\" path=\".awa\u002Fspecs\u002FARCHITECTURE.md\" \u002F>\n\u003Cfile type=\"feat\" path=\".awa\u002Fspecs\u002FFEAT-{CODE}-{feature-name}.md\" required=\"true\" \u002F>\n\u003Cfile type=\"examples\" path=\".awa\u002Fspecs\u002FEXAMPLE-{CODE}-{feature-name}-{nnn}.md\" required=\"if relevant\" \u002F>\n\u003Cfile type=\"requirements\" path=\".awa\u002Fspecs\u002FREQ-{CODE}-{feature-name}.md\" required=\"if relevant\" \u002F>\n\u003Cfile type=\"code\" required=\"if reverse workflow\" \u002F>\n\n## Action\n\nCreate or update the requirements document(s) as specified in the instruction above, following awa conventions.\nConsider existing specifications before making changes.\n\nIf deriving from existing code (reverse workflow), analyze the codebase to extract implicit requirements, acceptance criteria, and behavioral expectations.\n\n## Outputs\n\n\u003Cfile path=\".awa\u002Fspecs\u002FREQ-{CODE}-{feature-name}.md\" \u002F>\n\n## Rules\n\nYou SHALL ensure the {CODE} matches the corresponding FEAT {CODE} for the same feature if one exists.\nYou SHALL run `awa spec codes` to help choose the {CODE} extending existing one if logical.\nYou SHALL read the corresponding FEAT document before writing requirements.\nYou SHALL solidify requirements with respect to architecture, feature context, and existing requirements.\nYou SHALL create set of requirements in EARS format (INCOSE-compliant) based on the feature context.\nYou SHALL identify existing requirements to update, or new requirements to create.\nYou SHALL consider edge cases, UX, technical constraints, success criteria.\nYou SHOULD focus on requirements which will later be turned into a design.\nYou SHOULD keep requirements at a manageable level of detail.\nYou SHALL ensure requirement IDs and AC IDs follow the format defined in the traceability chain (e.g. `{CODE}-{n}`, `{CODE}-{n}_AC-{m}`, `{CODE}-{n}.{p}_AC-{m}`).\nYou SHALL support reverse workflow: deriving requirements from existing code when requested.\nYou SHALL clarify open points with user.\nYou MAY use todos and tools as needed.\n","# Create or Update Requirements\n\n## Bootstrap\n\n\u003Ctool name=\"read_file\">\n \u003Cread path=\".awa\u002F.agent\u002Fawa.core.md\" required=\"true\" error=\"on not found\" \u002F>\n \u003Cread path=\".awa\u002Frules\u002F*.md\" required=\"true\" \u002F>\n \u003Cread path=\".awa\u002Fspecs\u002FARCHITECTURE.md\" required=\"true\" error=\"on not found\" \u002F>\n \u003Cread path=\".awa\u002F.agent\u002Fschemas\u002FREQ.schema.yaml\" required=\"true\" error=\"on not found\" \u002F>\n\u003C\u002Ftool>\n\n## User Input\n\n```text\n${input}\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Inputs\n\n\u003Cfile type=\"architecture\" path=\".awa\u002Fspecs\u002FARCHITECTURE.md\" \u002F>\n\u003Cfile type=\"feat\" path=\".awa\u002Fspecs\u002FFEAT-{CODE}-{feature-name}.md\" required=\"true\" \u002F>\n\u003Cfile type=\"examples\" path=\".awa\u002Fspecs\u002FEXAMPLE-{CODE}-{feature-name}-{nnn}.md\" required=\"if relevant\" \u002F>\n\u003Cfile type=\"requirements\" path=\".awa\u002Fspecs\u002FREQ-{CODE}-{feature-name}.md\" required=\"if relevant\" \u002F>\n\u003Cfile type=\"code\" required=\"if reverse workflow\" \u002F>\n\n## Action\n\nCreate or update the requirements document(s) as specified in the instruction above, following awa conventions.\nConsider existing specifications before making changes.\n\nIf deriving from existing code (reverse workflow), analyze the codebase to extract implicit requirements, acceptance criteria, and behavioral expectations.\n\n## Outputs\n\n\u003Cfile path=\".awa\u002Fspecs\u002FREQ-{CODE}-{feature-name}.md\" \u002F>\n\n## Rules\n\nYou SHALL ensure the {CODE} matches the corresponding FEAT {CODE} for the same feature if one exists.\nYou SHALL run `awa spec codes` to help choose the {CODE} extending existing one if logical.\nYou SHALL read the corresponding FEAT document before writing requirements.\nYou SHALL solidify requirements with respect to architecture, feature context, and existing requirements.\nYou SHALL create set of requirements in EARS format (INCOSE-compliant) based on the feature context.\nYou SHALL identify existing requirements to update, or new requirements to create.\nYou SHALL consider edge cases, UX, technical constraints, success criteria.\nYou SHOULD focus on requirements which will later be turned into a design.\nYou SHOULD keep requirements at a manageable level of detail.\nYou SHALL ensure requirement IDs and AC IDs follow the format defined in the traceability chain (e.g. `{CODE}-{n}`, `{CODE}-{n}_AC-{m}`, `{CODE}-{n}.{p}_AC-{m}`).\nYou SHALL support reverse workflow: deriving requirements from existing code when requested.\nYou SHALL clarify open points with user.\nYou MAY use todos and tools as needed.\n",{"name":5,"description":7},"main","bea98700680b1eafbad3f739117ef66e30c4b9ae","templates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-requirements",0,"https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa","https:\u002F\u002Fgithub.com\u002Fncoderz","https:\u002F\u002Fncoderz.com","2026-08-13 06:47:47",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ncoderz\u002Fawa --skill awa-requirements",{"tool":42,"command":43},"bunx","bunx skills add ncoderz\u002Fawa --skill awa-requirements",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ncoderz\u002Fawa --skill awa-requirements","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-requirements\u002FSKILL.md",true,[],[51,66,77,88,101,111],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":23},"01M6C4ZTJ9714M6WEBACQTV8ED","awa-vibe","Implement an idea from start to finish using the full awa workflow. Use this when asked to take an idea through the complete development cycle.","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-vibe\u002FSKILL.md",[],[58,59,22,60,61,62,63,64,65],"awa vibe","vibe","start","development","workflow","implement","finish","take",{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":23},"01M6C4ZQZR114ABJE8HP0S0BDJ","awa-usage","Understand awa, its CLI, and configuration. Use this when asked about awa itself, how to use it, or how to configure it.","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-usage\u002FSKILL.md",[],[73,22,74,75,76],"awa usage","configure","how","cli",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":23},"01M6C4ZPBC19QXDJ09KW3Z18QR","awa-upgrade","Upgrade specs to match current schemas. Use this when asked to upgrade, migrate, or update specification documents to conform to schema changes.","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-upgrade\u002FSKILL.md",[],[84,85,22,86,87,21,19],"awa upgrade","schema","migrate","update specification",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":23},"01M6C4ZM0E11A21P1ZQPDNSS9J","awa-tasks","Create or update task list documents. Use this when asked to create tasks, generate implementation steps, or break down requirements and designs into work items.","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-tasks\u002FSKILL.md",[],[95,96,22,97,98,99,21,100,20,19],"awa tasks","tasks","list","work","create tasks","generate",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":23},"01M6C4ZJKZ7VHHX22G1WX6Z6HD","awa-spec-tidy","Tidy and reorganise the specifications logically. Use this when asked to tidy or reorganise the specifications.","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-spec-tidy\u002FSKILL.md",[],[108,109,110,22],"spec","awa spec tidy","tidy",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":23},"01M6C4ZH1RWPRW21G4RBWTX73M","awa-spec-merge","Merge two feature codes into one. Use this when asked to combine, merge, or consolidate feature codes.","https:\u002F\u002Fgithub.com\u002Fncoderz\u002Fawa\u002Fblob\u002Fmain\u002Ftemplates\u002Fawa\u002F_tests\u002Fcopilot\u002F.github\u002Fskills\u002Fawa-spec-merge\u002FSKILL.md",[],[118,108,119,22],"merge","awa spec merge"]