[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSKYWD7B0MH61FKKCNDN2Q":3,"skill-same:01M6FSKYWD7B0MH61FKKCNDN2Q":73},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6FSKYWD7B0MH61FKKCNDN2Q","openspec",null,"Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows. Supports custom schemas (TDD, rapid, etc.). Trigger on requests involving feature planning, spec writing, change management, or when \u002Fopsx commands are mentioned.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjcorrego\u002Fopenspec\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"use","spec-driven","with","feature planning","proposal","trigger","feature","commands","spec writing","design","change management","work","planning","development","tasks","change","workflows","cli","writing","2026-11-10 10:12:30",false,"---\nname: openspec\ndescription: Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows. Supports custom schemas (TDD, rapid, etc.). Trigger on requests involving feature planning, spec writing, change management, or when \u002Fopsx commands are mentioned.\n---\n\n# OpenSpec — Spec-Driven Development\n\nOpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation.\n\n## Setup\n\n```bash\n# Install globally\nnpm install -g @fission-ai\u002Fopenspec@latest\n\n# Initialize in a project\ncd \u002Fpath\u002Fto\u002Fproject\nopenspec init --tools claude\n\n# Update after CLI upgrade\nopenspec update\n```\n\n## Core Workflow\n\nEach change follows: **new → plan → apply → verify → archive**\n\n### 1. Start a Change\n\n```bash\n# Create change folder with default schema\nopenspec new change \u003Cname>\n\n# With specific schema\nopenspec new change \u003Cname> --schema tdd-driven\n```\n\n### 2. Plan (Create Artifacts)\n\nUse the CLI `instructions` command to get enriched prompts for each artifact:\n\n```bash\n# Get instructions for next artifact\nopenspec instructions --change \u003Cname> --json\n\n# Check progress\nopenspec status --change \u003Cname> --json\n```\n\n**Artifact sequence (spec-driven schema):**\n1. `proposal.md` — Why and what (intent, scope, approach)\n2. `specs\u002F` — Requirements + scenarios (Given\u002FWhen\u002FThen)\n3. `design.md` — Technical approach and architecture decisions\n4. `tasks.md` — Implementation checklist with checkboxes\n\n### 3. Implement\n\nRead `tasks.md` and work through items, marking `[x]` as complete.\n\n### 4. Verify\n\n```bash\nopenspec validate --change \u003Cname> --json\n```\n\nChecks completeness, correctness, and coherence.\n\n### 5. Archive\n\n```bash\nopenspec archive \u003Cname> --yes\n```\n\nMerges delta specs into main `openspec\u002Fspecs\u002F` and moves change to archive.\n\n## Agent Workflow (How to Use as an AI Agent)\n\nWhen the user asks to build\u002Fmigrate\u002Frefactor something with OpenSpec:\n\n1. **Check project state:**\n   ```bash\n   openspec list --json           # Active changes\n   openspec list --specs --json   # Current specs\n   openspec schemas --json        # Available schemas\n   ```\n\n2. **Create the change:**\n   ```bash\n   openspec new change \u003Cname> [--schema \u003Cschema>]\n   ```\n\n3. **For each artifact**, get instructions and create the file:\n   ```bash\n   openspec instructions \u003Cartifact> --change \u003Cname> --json\n   openspec status --change \u003Cname> --json\n   ```\n   Then write the artifact file to `openspec\u002Fchanges\u002F\u003Cname>\u002F`.\n\n4. **Implement** tasks from `tasks.md`.\n\n5. **Validate and archive:**\n   ```bash\n   openspec validate \u003Cname> --json\n   openspec archive \u003Cname> --yes\n   ```\n\n## CLI Quick Reference\n\n| Command | Purpose |\n|---------|---------|\n| `openspec list [--specs] [--json]` | List changes or specs |\n| `openspec show \u003Cname> [--json]` | Show change\u002Fspec details |\n| `openspec status --change \u003Cname> [--json]` | Artifact completion status |\n| `openspec instructions [artifact] --change \u003Cname> [--json]` | Get enriched creation instructions |\n| `openspec validate [name] [--all] [--json]` | Validate changes\u002Fspecs |\n| `openspec archive \u003Cname> [--yes]` | Archive completed change |\n| `openspec schemas [--json]` | List available schemas |\n| `openspec templates [--json]` | Show template paths |\n| `openspec config` | View\u002Fmodify settings |\n\nAlways use `--json` for programmatic\u002Fagent use.\n\n## Custom Schemas\n\nSchemas define artifact sequences. Create custom ones for different workflows:\n\n```bash\n# Fork built-in schema\nopenspec schema fork spec-driven my-workflow\n\n# Create from scratch\nopenspec schema init my-workflow\n\n# Validate\nopenspec schema validate my-workflow\n```\n\nSchema files live in `openspec\u002Fschemas\u002F\u003Cname>\u002Fschema.yaml` with templates in `templates\u002F`.\n\nFor schema structure details, see [references\u002Fschemas.md](references\u002Fschemas.md).\n\n## Project Structure\n\n```\nproject\u002F\n├── openspec\u002F\n│   ├── config.yaml          # Project config (default schema, context, rules)\n│   ├── specs\u002F               # Source of truth — current system behavior\n│   ├── changes\u002F             # Active changes (one folder each)\n│   │   └── \u003Cchange-name>\u002F\n│   │       ├── .openspec.yaml\n│   │       ├── proposal.md\n│   │       ├── specs\u002F       # Delta specs (what's changing)\n│   │       ├── design.md\n│   │       └── tasks.md\n│   └── schemas\u002F             # Custom schemas\n└── .claude\u002Fskills\u002F          # Auto-generated Claude integration\n```\n\n## Spec Format\n\nSpecs use RFC 2119 keywords (SHALL\u002FMUST\u002FSHOULD\u002FMAY) with Given\u002FWhen\u002FThen scenarios:\n\n```markdown\n### Requirement: User Authentication\nThe system SHALL issue a JWT token upon successful login.\n\n#### Scenario: Valid credentials\n- GIVEN a user with valid credentials\n- WHEN the user submits login form\n- THEN a JWT token is returned\n```\n\n## Delta Specs\n\nChanges don't rewrite specs — they describe deltas (ADDED\u002FMODIFIED\u002FREMOVED) that merge into main specs on archive.\n\n## Config\n\n`openspec\u002Fconfig.yaml` sets defaults:\n\n```yaml\nschema: spec-driven      # or tdd-driven, rapid, custom\ncontext: |\n  Tech stack: TypeScript, React, Node.js\n  Testing: Jest\nrules:\n  proposal:\n    - Include rollback plan\n  specs:\n    - Use Given\u002FWhen\u002FThen format\n```\n","# OpenSpec — Spec-Driven Development\n\nOpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation.\n\n## Setup\n\n```bash\n# Install globally\nnpm install -g @fission-ai\u002Fopenspec@latest\n\n# Initialize in a project\ncd \u002Fpath\u002Fto\u002Fproject\nopenspec init --tools claude\n\n# Update after CLI upgrade\nopenspec update\n```\n\n## Core Workflow\n\nEach change follows: **new → plan → apply → verify → archive**\n\n### 1. Start a Change\n\n```bash\n# Create change folder with default schema\nopenspec new change \u003Cname>\n\n# With specific schema\nopenspec new change \u003Cname> --schema tdd-driven\n```\n\n### 2. Plan (Create Artifacts)\n\nUse the CLI `instructions` command to get enriched prompts for each artifact:\n\n```bash\n# Get instructions for next artifact\nopenspec instructions --change \u003Cname> --json\n\n# Check progress\nopenspec status --change \u003Cname> --json\n```\n\n**Artifact sequence (spec-driven schema):**\n1. `proposal.md` — Why and what (intent, scope, approach)\n2. `specs\u002F` — Requirements + scenarios (Given\u002FWhen\u002FThen)\n3. `design.md` — Technical approach and architecture decisions\n4. `tasks.md` — Implementation checklist with checkboxes\n\n### 3. Implement\n\nRead `tasks.md` and work through items, marking `[x]` as complete.\n\n### 4. Verify\n\n```bash\nopenspec validate --change \u003Cname> --json\n```\n\nChecks completeness, correctness, and coherence.\n\n### 5. Archive\n\n```bash\nopenspec archive \u003Cname> --yes\n```\n\nMerges delta specs into main `openspec\u002Fspecs\u002F` and moves change to archive.\n\n## Agent Workflow (How to Use as an AI Agent)\n\nWhen the user asks to build\u002Fmigrate\u002Frefactor something with OpenSpec:\n\n1. **Check project state:**\n   ```bash\n   openspec list --json           # Active changes\n   openspec list --specs --json   # Current specs\n   openspec schemas --json        # Available schemas\n   ```\n\n2. **Create the change:**\n   ```bash\n   openspec new change \u003Cname> [--schema \u003Cschema>]\n   ```\n\n3. **For each artifact**, get instructions and create the file:\n   ```bash\n   openspec instructions \u003Cartifact> --change \u003Cname> --json\n   openspec status --change \u003Cname> --json\n   ```\n   Then write the artifact file to `openspec\u002Fchanges\u002F\u003Cname>\u002F`.\n\n4. **Implement** tasks from `tasks.md`.\n\n5. **Validate and archive:**\n   ```bash\n   openspec validate \u003Cname> --json\n   openspec archive \u003Cname> --yes\n   ```\n\n## CLI Quick Reference\n\n| Command | Purpose |\n|---------|---------|\n| `openspec list [--specs] [--json]` | List changes or specs |\n| `openspec show \u003Cname> [--json]` | Show change\u002Fspec details |\n| `openspec status --change \u003Cname> [--json]` | Artifact completion status |\n| `openspec instructions [artifact] --change \u003Cname> [--json]` | Get enriched creation instructions |\n| `openspec validate [name] [--all] [--json]` | Validate changes\u002Fspecs |\n| `openspec archive \u003Cname> [--yes]` | Archive completed change |\n| `openspec schemas [--json]` | List available schemas |\n| `openspec templates [--json]` | Show template paths |\n| `openspec config` | View\u002Fmodify settings |\n\nAlways use `--json` for programmatic\u002Fagent use.\n\n## Custom Schemas\n\nSchemas define artifact sequences. Create custom ones for different workflows:\n\n```bash\n# Fork built-in schema\nopenspec schema fork spec-driven my-workflow\n\n# Create from scratch\nopenspec schema init my-workflow\n\n# Validate\nopenspec schema validate my-workflow\n```\n\nSchema files live in `openspec\u002Fschemas\u002F\u003Cname>\u002Fschema.yaml` with templates in `templates\u002F`.\n\nFor schema structure details, see [references\u002Fschemas.md](references\u002Fschemas.md).\n\n## Project Structure\n\n```\nproject\u002F\n├── openspec\u002F\n│   ├── config.yaml          # Project config (default schema, context, rules)\n│   ├── specs\u002F               # Source of truth — current system behavior\n│   ├── changes\u002F             # Active changes (one folder each)\n│   │   └── \u003Cchange-name>\u002F\n│   │       ├── .openspec.yaml\n│   │       ├── proposal.md\n│   │       ├── specs\u002F       # Delta specs (what's changing)\n│   │       ├── design.md\n│   │       └── tasks.md\n│   └── schemas\u002F             # Custom schemas\n└── .claude\u002Fskills\u002F          # Auto-generated Claude integration\n```\n\n## Spec Format\n\nSpecs use RFC 2119 keywords (SHALL\u002FMUST\u002FSHOULD\u002FMAY) with Given\u002FWhen\u002FThen scenarios:\n\n```markdown\n### Requirement: User Authentication\nThe system SHALL issue a JWT token upon successful login.\n\n#### Scenario: Valid credentials\n- GIVEN a user with valid credentials\n- WHEN the user submits login form\n- THEN a JWT token is returned\n```\n\n## Delta Specs\n\nChanges don't rewrite specs — they describe deltas (ADDED\u002FMODIFIED\u002FREMOVED) that merge into main specs on archive.\n\n## Config\n\n`openspec\u002Fconfig.yaml` sets defaults:\n\n```yaml\nschema: spec-driven      # or tdd-driven, rapid, custom\ncontext: |\n  Tech stack: TypeScript, React, Node.js\n  Testing: Jest\nrules:\n  proposal:\n    - Include rollback plan\n  specs:\n    - Use Given\u002FWhen\u002FThen format\n```\n",{"name":5,"description":7},"main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fjcorrego\u002Fopenspec",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add kbarbel640-del\u002Fskills --skill openspec",{"tool":55,"command":56},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill openspec",{"tool":58,"command":59},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill openspec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjcorrego\u002Fopenspec\u002FSKILL.md",true,[63,69],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"_meta.json","REFERENCE","参考文档",270,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjcorrego\u002Fopenspec\u002F_meta.json",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fschemas.md",3256,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjcorrego\u002Fopenspec\u002Freferences\u002Fschemas.md",[74,104,131,152,158,178],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":37},"01M6G8J55967D6281ACMKAKTEQ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[86,87,88,20,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103],"crowd prompting","prompting","api","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"publishedAt":37},"01M6G8J0PKPAYVET6BWE8W4C26","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[116,88,117,118,119,120,121,122,123,124,125,27,126,127,128,129,130,92,18],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","openclaw","strategy","headless","compete","submit","matchmaking",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":37},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000021","资料检索与研究",[141,142,143,144,145,146,147,20,148,129,18,149,88,150,151],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":153,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":37},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[156],{"categoryNo":138,"categoryName":139,"taxonomyType":113,"taxonomyTypeDesc":114},[144,143,142,141,151,146,147,20,145,129,18,148,149,88,150],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":37},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[165,166,167,168,169,170,171,172,173,174,175,176,177],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":188,"publishedAt":37},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[184,185],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},{"categoryNo":186,"categoryName":187,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000037","律师与法务",[189,190,191,192,20,193,194,42,195,149,196,197,198,199,200,101,201,202,203],"agent constitution","constitution","contracts","tree","query","base","log","check","Rules","projects","compliance","actions","state","governance","github"]