[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DF2ZNC2B1WN2A7SVRQC7Y0":3,"skill-same:01M7DF2ZNC2B1WN2A7SVRQC7Y0":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DF2ZNC2B1WN2A7SVRQC7Y0","plan",null,"Paved command paved.plan. Draft and preview a plan for an open Intent, then record the user's explicit approval. Use when an Intent is ready for planning.","andersonmrodrigues\u002Fpaved","andersonmrodrigues","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13907380?v=4","01M7DEV3FP2VMQZ3FP2FP1TK1C","Anderson Rodrigues","01M7DEV3GC2QAQBW4FMNT98H48",1,"MIT","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fpaved\u002Fskills\u002Fplan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan\ndescription: \"Paved command paved.plan. Draft and preview a plan for an open Intent, then record the user's explicit approval. Use when an Intent is ready for planning.\"\n---\n\u003C!-- Generated by Paved plugin paved@2.29.0 from paved.plan; edit Paved Core instead. -->\n# Paved `plan` command (paved.plan)\n\nDraft and preview a plan for an open Intent, then record the user's explicit approval. Use when an Intent is ready for planning.\n\n**Input:** The run, when several are open (--run \u003Cid>).\n**Output:** The plan awaiting approval, its review block, and the approval outcome.\n**Required lifecycle:** RESOLVED, GENERATED, VALIDATED, READY\n**Required context:** .paved\u002Fproject\u002F, .paved\u002Frules\u002F, the run's workflow, verification profile\n**Required capabilities:** none declared\n**Allowed side effects:** .paved\u002Fdocuments\u002Fplans\u002F, .paved\u002Fapprovals\u002F, .paved\u002Fgenerated\u002Fruns\u002F\n\n## Execution contract\n\n1. Invoke `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpaved.mjs\" plan --json` from the repository root, passing the user's command inputs as supported CLI arguments. The launcher loads the pinned project-local runtime and returns the canonical structured result. Always run it from the repository being worked on, never from the plugin directory.\n2. Follow the structured result's status, diagnostics, evidence, and next action. When `data.remediation` names a Paved command, run it right away, present any decisions it returns, then repeat the original command. Stop only when the runtime blocks on something it cannot remediate.\n3. Read the run's Intent document at `.paved\u002Fdocuments\u002Fintents\u002F\u003Crun-id>.md`, then write a plan that answers it and links to it. Save the plan at `.paved\u002Fdocuments\u002Fplans\u002F\u003Crun-id>.md` and run this command with `--advance --evidence \u003Cplan> --note \u003Csummary>`. When the result carries a `review` block, start the preview on its target (with its companions) and follow the `paved.preview` review loop without ending your turn: resolve each comment after editing and advance once after edits so the approval request covers the current plan. When the user approves the plan in the conversation with an explicit yes, run `paved plan --run \u003Crun-id> --approve --json`; never approve on your own or on an ambiguous reply.\n\n## Phase Tool policies\n\nFollow the active `data.phaseContext`, including its composed skills, declared Tools and bound fragment bodies. Apply each `phaseContext.toolPolicies` entry's effective `allow`, `ask` and `deny` Tool ids: `deny` excludes use; `ask` requires the host's own approval flow; `allow` is a workflow recommendation only and never grants execution permission or replaces host approval. Host policy can always be stricter. Policies do not add Tools to the phase's declared set. Omitted Tools retain existing host behavior, and an empty policy list preserves existing behavior.\n\n## Run autonomy\n\nFor a new intent or execute request, pass the user's explicit `--autonomy \u003Cguided|balanced|autonomous>` selection. It overrides the workflow's optional `autonomy.default_profile`; pending classification preserves the explicit selection. The recorded `data.autonomy_profile` is fixed on resume. If no selection or workflow default exists, leave the profile absent and keep current behavior.\nFor `guided`, stop after every completed phase and wait for the user to advance; do not immediately repeat `--auto` or another advance call. For `balanced`, continue through ready phases with `execute --auto`. For `autonomous`, use balanced continuation and automatically dispatch only ready tasks from an approved delegation plan, respecting its dependencies and bounded scope, through native host tools. The CLI creates no sessions.\nEvery profile preserves gates, human approvals, required input stops, failures, verification, evidence and completion requirements. Host permissions remain authoritative; an autonomy profile is never an approval or tool permission. Apply this policy to the continuation and routing guidance above.\n\n## Before asking the user\n\nTriage every question of your own before you ask it. When the answer is observable (current behavior, output, timing, layout, whether a test fails), find it out by reading the code, running it or trying a throwaway experiment outside the repository; an experiment inside the repository follows the `prototyping` skill. Ask only about preferences: product, scope, priority or taste calls that no experiment settles. When you raise one with `paved decision raise`, set `questionKind`; an `observable` question needs an `observationBlocker` saying why you could not observe it. Triage never skips a human step: present every decision Paved emits, and plan approval and confirmation of destructive actions stay with the user.\n\n## Failure behavior\n\n- A plan file and summary are required before approval.\n- A changed plan needs a new approval.\n- Only the user approves, in the conversation.\n- If a required ToolImplementation or runtime is unavailable, stop and explain the missing prerequisite. Never infer or execute a command from repository scripts.\n- Do not edit human-owned Paved state or bypass lifecycle, ownership, approval, or verification gates.\n\n## Conversational contract\n\n1. Invoke the command. If it returns `\"status\": \"awaiting_input\"`, it is waiting on the user.\n2. Present every decision in `decisions[]` to the user: what Paved detected, what\n   remains to decide, why it matters, the options, Paved's recommendation and its evidence.\n3. Collect the user's answer. Do not answer on their behalf.\n4. Resume the same command with `--answer \u003Cdecision-id>=\u003Cvalue> --answered-by \u003Cidentity>`,\n   repeating `--answer` once per value for a multi-choice decision.\n5. Present the result.\n\nFollow `core.decisions.decisions` for the full interaction protocol and its prohibitions.\n","\u003C!-- Generated by Paved plugin paved@2.29.0 from paved.plan; edit Paved Core instead. -->\n# Paved `plan` command (paved.plan)\n\nDraft and preview a plan for an open Intent, then record the user's explicit approval. Use when an Intent is ready for planning.\n\n**Input:** The run, when several are open (--run \u003Cid>).\n**Output:** The plan awaiting approval, its review block, and the approval outcome.\n**Required lifecycle:** RESOLVED, GENERATED, VALIDATED, READY\n**Required context:** .paved\u002Fproject\u002F, .paved\u002Frules\u002F, the run's workflow, verification profile\n**Required capabilities:** none declared\n**Allowed side effects:** .paved\u002Fdocuments\u002Fplans\u002F, .paved\u002Fapprovals\u002F, .paved\u002Fgenerated\u002Fruns\u002F\n\n## Execution contract\n\n1. Invoke `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpaved.mjs\" plan --json` from the repository root, passing the user's command inputs as supported CLI arguments. The launcher loads the pinned project-local runtime and returns the canonical structured result. Always run it from the repository being worked on, never from the plugin directory.\n2. Follow the structured result's status, diagnostics, evidence, and next action. When `data.remediation` names a Paved command, run it right away, present any decisions it returns, then repeat the original command. Stop only when the runtime blocks on something it cannot remediate.\n3. Read the run's Intent document at `.paved\u002Fdocuments\u002Fintents\u002F\u003Crun-id>.md`, then write a plan that answers it and links to it. Save the plan at `.paved\u002Fdocuments\u002Fplans\u002F\u003Crun-id>.md` and run this command with `--advance --evidence \u003Cplan> --note \u003Csummary>`. When the result carries a `review` block, start the preview on its target (with its companions) and follow the `paved.preview` review loop without ending your turn: resolve each comment after editing and advance once after edits so the approval request covers the current plan. When the user approves the plan in the conversation with an explicit yes, run `paved plan --run \u003Crun-id> --approve --json`; never approve on your own or on an ambiguous reply.\n\n## Phase Tool policies\n\nFollow the active `data.phaseContext`, including its composed skills, declared Tools and bound fragment bodies. Apply each `phaseContext.toolPolicies` entry's effective `allow`, `ask` and `deny` Tool ids: `deny` excludes use; `ask` requires the host's own approval flow; `allow` is a workflow recommendation only and never grants execution permission or replaces host approval. Host policy can always be stricter. Policies do not add Tools to the phase's declared set. Omitted Tools retain existing host behavior, and an empty policy list preserves existing behavior.\n\n## Run autonomy\n\nFor a new intent or execute request, pass the user's explicit `--autonomy \u003Cguided|balanced|autonomous>` selection. It overrides the workflow's optional `autonomy.default_profile`; pending classification preserves the explicit selection. The recorded `data.autonomy_profile` is fixed on resume. If no selection or workflow default exists, leave the profile absent and keep current behavior.\nFor `guided`, stop after every completed phase and wait for the user to advance; do not immediately repeat `--auto` or another advance call. For `balanced`, continue through ready phases with `execute --auto`. For `autonomous`, use balanced continuation and automatically dispatch only ready tasks from an approved delegation plan, respecting its dependencies and bounded scope, through native host tools. The CLI creates no sessions.\nEvery profile preserves gates, human approvals, required input stops, failures, verification, evidence and completion requirements. Host permissions remain authoritative; an autonomy profile is never an approval or tool permission. Apply this policy to the continuation and routing guidance above.\n\n## Before asking the user\n\nTriage every question of your own before you ask it. When the answer is observable (current behavior, output, timing, layout, whether a test fails), find it out by reading the code, running it or trying a throwaway experiment outside the repository; an experiment inside the repository follows the `prototyping` skill. Ask only about preferences: product, scope, priority or taste calls that no experiment settles. When you raise one with `paved decision raise`, set `questionKind`; an `observable` question needs an `observationBlocker` saying why you could not observe it. Triage never skips a human step: present every decision Paved emits, and plan approval and confirmation of destructive actions stay with the user.\n\n## Failure behavior\n\n- A plan file and summary are required before approval.\n- A changed plan needs a new approval.\n- Only the user approves, in the conversation.\n- If a required ToolImplementation or runtime is unavailable, stop and explain the missing prerequisite. Never infer or execute a command from repository scripts.\n- Do not edit human-owned Paved state or bypass lifecycle, ownership, approval, or verification gates.\n\n## Conversational contract\n\n1. Invoke the command. If it returns `\"status\": \"awaiting_input\"`, it is waiting on the user.\n2. Present every decision in `decisions[]` to the user: what Paved detected, what\n   remains to decide, why it matters, the options, Paved's recommendation and its evidence.\n3. Collect the user's answer. Do not answer on their behalf.\n4. Resume the same command with `--answer \u003Cdecision-id>=\u003Cvalue> --answered-by \u003Cidentity>`,\n   repeating `--answer` once per value for a multi-choice decision.\n5. Present the result.\n\nFollow `core.decisions.decisions` for the full interaction protocol and its prohibitions.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","plugins\u002Fclaude\u002Fpaved\u002Fskills\u002Fplan",0,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues","2026-11-14 20:09:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add andersonmrodrigues\u002Fpaved --skill plan",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill plan",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fpaved\u002Fskills\u002Fplan\u002FSKILL.md",true,[],[46,53,59,65,71,77],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DFBWJT4T1MPBHTWT19PBEK","sample-skill","Does a sample task. Use when a sample is needed.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7DFBFAD0RYCRHTZ2JW4RX7E","no-activation","Does a sample task.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fno-activation\u002FSKILL.md",[],[]]