[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N1171NB5CBCF9X58AN02D6":3,"skill-same:01M6N1171NB5CBCF9X58AN02D6":69},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6N1171NB5CBCF9X58AN02D6","plan-phase",null,"Turn a praxis design phase into a structured planning artifact. Use when starting or refining any of the 8 planning phases (API Scope and Positioning, Core Runtime, Interface Contracts, Observability and Errors, Security and Trust, Release and Community Governance, MCP Integration, Skills Integration). Produces objectives, key questions, decisions, assumptions, risks, deliverables, recommended subagents, and exit criteria.","praxis-os\u002Fpraxis","praxis-os","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273815985?v=4","01M6N11079A9C25VGW87C9666M","Praxis OS","01M6N110C54JDHGXWVA67HW8QN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan-phase\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"plan phase","plan","trust","errors","deliverables","interface","scope","runtime","positioning","community","exit","design","use","decisions","api","MCP Integration","observability","planning","core","MCP","2026-11-10 10:12:30",false,"---\nname: plan-phase\ndescription: >\n  Turn a praxis design phase into a structured planning artifact. Use when starting or\n  refining any of the 8 planning phases (API Scope and Positioning, Core Runtime,\n  Interface Contracts, Observability and Errors, Security and Trust, Release and\n  Community Governance, MCP Integration, Skills Integration). Produces objectives,\n  key questions, decisions, assumptions, risks, deliverables, recommended subagents,\n  and exit criteria.\n---\n\n# Plan Phase\n\nProduce a concrete planning artifact for a single design phase of the `praxis` Go library.\n\n## Input\n\nAccept a phase name or topic. If ambiguous, ask for clarification before proceeding.\n\n## Output Structure\n\nUse this exact structure:\n\n```\n# Phase: \u003Cname>\n\n## Goal\nOne sentence stating the phase objective — what the phase must produce to unblock v1.0.\n\n## Scope\nBullet list of what is in scope and what is explicitly out of scope. Reference which\nparts of `docs\u002FPRAXIS-SEED-CONTEXT.md` this phase refines.\n\n## Key Questions\nNumbered list of open questions that must be answered to close this phase. Phrase them\nas questions that have concrete answers, not wishlists.\n\n## Decisions Required\nNumbered list of decisions with brief context for each. Use `DNN` identifiers (D01, D02, ...)\nthat stay unique across phases.\n\n## Assumptions\nBullet list of assumptions being made. Flag any that are weak or unvalidated.\n\n## Risks\nBullet list. Separate critical risks (block v1.0 or break the decoupling contract) from\nsecondary risks.\n\n## Deliverables\nBullet list of expected output files. All files use the `NN-filename.md` convention.\n`REVIEW.md` is the only unnumbered file.\n\n## Recommended Subagents\nList 1-2 subagents from: api-designer, go-architect, security-architect,\nobservability-architect, dx-designer, solution-researcher.\nJustify each recommendation in one sentence.\nThe reviewer subagent is always invoked — do not list it here.\n\n## Exit Criteria\nNumbered list of conditions that must be true for the phase to be considered complete.\nInclude: all decisions locked, reviewer PASS, REVIEW.md verdict READY, no banned-identifier\nleakage in phase artifacts.\n```\n\n## Deliverable Naming Convention\n\nAll phase output files must be numbered with a two-digit prefix to enforce reading order.\nFormat: `NN-filename.md` (e.g., `01-decisions-log.md`, `02-state-machine.md`).\n\nThe `Deliverables` section of the planning artifact must list files in numbered order.\n`REVIEW.md` is the only file without a number prefix — it is always the last file in the\nphase directory.\n\n## Guardrails\n\n- Do not generate implementation code. This is a design harness.\n- Do not invent technical detail unless necessary to frame a question or risk.\n- Do not expand scope beyond what the phase requires. Refer ambiguous scope back to\n  `docs\u002FPRAXIS-SEED-CONTEXT.md` — it is the source of truth.\n- Do not propose more than 2 specialist subagents unless truly justified.\n- Identify ambiguity explicitly rather than papering over it.\n- Respect the decoupling contract: no `custos`, `reef`, `governance_event`, hardcoded\n  `org.id`\u002F`agent.id` leakage. Phase artifacts must pass the banned-identifier grep.\n- Prefer clarity over completeness theater. OSS libraries fail when over-designed.\n- Focus on planning, not implementation.\n\n## Phase Reference\n\n1. **API Scope and Positioning** — what `praxis` is, positioning vs existing Go libraries,\n   design principles, target consumers, what v1.0 commits to, what is explicitly non-goal.\n2. **Core Runtime Design** — invocation state machine, lifecycle, streaming transport,\n   cancellation semantics, context propagation, concurrency model.\n3. **Interface Contracts** — all public v1.0 interfaces (AgentOrchestrator, LLMProvider,\n   tools.Invoker, hooks.PolicyHook, hooks.PreLLMFilter, hooks.PostToolFilter, budget.Guard,\n   budget.PriceProvider, errors.TypedError, errors.Classifier, telemetry.LifecycleEventEmitter,\n   telemetry.AttributeEnricher, credentials.Resolver, identity.Signer), their method\n   surfaces, default\u002Fnull implementations, composability rules.\n4. **Observability and Error Model** — OTel span structure, Prometheus metrics, slog\n   redaction, typed error taxonomy, error-to-event mapping, `AttributeEnricher` contract,\n   cardinality constraints.\n5. **Security and Trust Boundaries** — credential fetch semantics, zero-on-close, identity\n   signing (Ed25519 JWT), untrusted tool output handling, filter hook trust model, key\n   lifecycle.\n6. **Release, Versioning and Community Governance** — semver policy, v0 to v1.0 stability\n   commitment, deprecation windows, v2+ module path rules, release process (conventional\n   commits + release-please), CI pipeline (lint, test, coverage, benchmarks, banned-identifier\n   grep, govulncheck, codeql), contribution model, code of conduct, RFC process.\n\n## Reference inputs\n\nEvery plan-phase invocation should read:\n\n- `docs\u002FPRAXIS-SEED-CONTEXT.md` — the foundational context document. It contains the\n  vision, design principles, interface surface summary, decoupling contract, and initial\n  roadmap. Phases refine this document, they do not override it.\n- Any previously approved phase in `docs\u002Fphase-\u003CN>-\u003Cslug>\u002F` — earlier decisions flow\n  forward and must not be contradicted without an explicit amendment.\n","# Plan Phase\n\nProduce a concrete planning artifact for a single design phase of the `praxis` Go library.\n\n## Input\n\nAccept a phase name or topic. If ambiguous, ask for clarification before proceeding.\n\n## Output Structure\n\nUse this exact structure:\n\n```\n# Phase: \u003Cname>\n\n## Goal\nOne sentence stating the phase objective — what the phase must produce to unblock v1.0.\n\n## Scope\nBullet list of what is in scope and what is explicitly out of scope. Reference which\nparts of `docs\u002FPRAXIS-SEED-CONTEXT.md` this phase refines.\n\n## Key Questions\nNumbered list of open questions that must be answered to close this phase. Phrase them\nas questions that have concrete answers, not wishlists.\n\n## Decisions Required\nNumbered list of decisions with brief context for each. Use `DNN` identifiers (D01, D02, ...)\nthat stay unique across phases.\n\n## Assumptions\nBullet list of assumptions being made. Flag any that are weak or unvalidated.\n\n## Risks\nBullet list. Separate critical risks (block v1.0 or break the decoupling contract) from\nsecondary risks.\n\n## Deliverables\nBullet list of expected output files. All files use the `NN-filename.md` convention.\n`REVIEW.md` is the only unnumbered file.\n\n## Recommended Subagents\nList 1-2 subagents from: api-designer, go-architect, security-architect,\nobservability-architect, dx-designer, solution-researcher.\nJustify each recommendation in one sentence.\nThe reviewer subagent is always invoked — do not list it here.\n\n## Exit Criteria\nNumbered list of conditions that must be true for the phase to be considered complete.\nInclude: all decisions locked, reviewer PASS, REVIEW.md verdict READY, no banned-identifier\nleakage in phase artifacts.\n```\n\n## Deliverable Naming Convention\n\nAll phase output files must be numbered with a two-digit prefix to enforce reading order.\nFormat: `NN-filename.md` (e.g., `01-decisions-log.md`, `02-state-machine.md`).\n\nThe `Deliverables` section of the planning artifact must list files in numbered order.\n`REVIEW.md` is the only file without a number prefix — it is always the last file in the\nphase directory.\n\n## Guardrails\n\n- Do not generate implementation code. This is a design harness.\n- Do not invent technical detail unless necessary to frame a question or risk.\n- Do not expand scope beyond what the phase requires. Refer ambiguous scope back to\n  `docs\u002FPRAXIS-SEED-CONTEXT.md` — it is the source of truth.\n- Do not propose more than 2 specialist subagents unless truly justified.\n- Identify ambiguity explicitly rather than papering over it.\n- Respect the decoupling contract: no `custos`, `reef`, `governance_event`, hardcoded\n  `org.id`\u002F`agent.id` leakage. Phase artifacts must pass the banned-identifier grep.\n- Prefer clarity over completeness theater. OSS libraries fail when over-designed.\n- Focus on planning, not implementation.\n\n## Phase Reference\n\n1. **API Scope and Positioning** — what `praxis` is, positioning vs existing Go libraries,\n   design principles, target consumers, what v1.0 commits to, what is explicitly non-goal.\n2. **Core Runtime Design** — invocation state machine, lifecycle, streaming transport,\n   cancellation semantics, context propagation, concurrency model.\n3. **Interface Contracts** — all public v1.0 interfaces (AgentOrchestrator, LLMProvider,\n   tools.Invoker, hooks.PolicyHook, hooks.PreLLMFilter, hooks.PostToolFilter, budget.Guard,\n   budget.PriceProvider, errors.TypedError, errors.Classifier, telemetry.LifecycleEventEmitter,\n   telemetry.AttributeEnricher, credentials.Resolver, identity.Signer), their method\n   surfaces, default\u002Fnull implementations, composability rules.\n4. **Observability and Error Model** — OTel span structure, Prometheus metrics, slog\n   redaction, typed error taxonomy, error-to-event mapping, `AttributeEnricher` contract,\n   cardinality constraints.\n5. **Security and Trust Boundaries** — credential fetch semantics, zero-on-close, identity\n   signing (Ed25519 JWT), untrusted tool output handling, filter hook trust model, key\n   lifecycle.\n6. **Release, Versioning and Community Governance** — semver policy, v0 to v1.0 stability\n   commitment, deprecation windows, v2+ module path rules, release process (conventional\n   commits + release-please), CI pipeline (lint, test, coverage, benchmarks, banned-identifier\n   grep, govulncheck, codeql), contribution model, code of conduct, RFC process.\n\n## Reference inputs\n\nEvery plan-phase invocation should read:\n\n- `docs\u002FPRAXIS-SEED-CONTEXT.md` — the foundational context document. It contains the\n  vision, design principles, interface surface summary, decoupling contract, and initial\n  roadmap. Phases refine this document, they do not override it.\n- Any previously approved phase in `docs\u002Fphase-\u003CN>-\u003Cslug>\u002F` — earlier decisions flow\n  forward and must not be contradicted without an explicit amendment.\n",{"name":5,"description":7},"main","26850a098b21b457e4829147b5a3d2d15966a38f",".claude\u002Fskills\u002Fplan-phase","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis","https:\u002F\u002Fgithub.com\u002Fpraxis-os","2026-04-16 16:28:03",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add praxis-os\u002Fpraxis --skill plan-phase",{"tool":61,"command":62},"bunx","bunx skills add praxis-os\u002Fpraxis --skill plan-phase",{"tool":64,"command":65},"pnpm","pnpm dlx skills add praxis-os\u002Fpraxis --skill plan-phase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan-phase\u002FSKILL.md",true,[],[70,97,107,117,123,133],{"skillNo":71,"name":72,"nameZh":6,"description":73,"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":44},"01M6N12GN1THXER5NWFYV5MHSD","code-reviewer","Reviews staged changes for correctness, test coverage, and style.","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002Fskills\u002Ftestdata\u002Fvalid-bundle\u002FSKILL.md",[],[77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"reviewer","code reviewer","code","for","opus","sonnet","changes","correctness","reviews","style","platform","staged","test coverage","example","coverage","read","grep","team","file","test",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":44},"01M6N12D8T1PR124NWWWZMD47C","missing-name","Skill without a name field.","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002Fskills\u002Ftestdata\u002Fmissing-name\u002FSKILL.md",[],[104,105,106],"missing","name","missing name",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":44},"01M6N12BN6PAJZJXCBQ5QGS9CS","minimal","A minimal skill with only required fields.","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002Fskills\u002Ftestdata\u002Fminimal-bundle\u002FSKILL.md",[],[109,114,115,116],"with","only","minimal skill",{"skillNo":118,"name":119,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":44},"01M6N1282ENSGYCH49EV2AR1AT","malformed","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002Fskills\u002Ftestdata\u002Fmalformed\u002FSKILL.md",[],[119],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":44},"01M6N1262W02EB4ZQDZEWAE4EW","with-extensions","Skill with unrecognised fields.","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002Fskills\u002Ftestdata\u002Fextension-fields\u002FSKILL.md",[],[130,131,114,132],"with extensions","extensions","high",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":44},"01M6N122M8YQVK0VR4TPANCQ92","empty-body","Skill with no instruction body.","https:\u002F\u002Fgithub.com\u002Fpraxis-os\u002Fpraxis\u002Fblob\u002Fmain\u002Fskills\u002Ftestdata\u002Fempty-body\u002FSKILL.md",[],[140,141,114],"empty","Empty body"]