# Send OpenSpec to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "openspec", "name": "OpenSpec", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/jcorrego/openspec", "canonicalUrl": "https://clawhub.ai/jcorrego/openspec", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/openspec", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openspec", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/schemas.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "openspec", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:37.338Z", "expiresAt": "2026-05-07T16:55:37.338Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openspec", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openspec", "contentDisposition": "attachment; filename=\"openspec-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "openspec" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/openspec" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/openspec", "downloadUrl": "https://openagent3.xyz/downloads/openspec", "agentUrl": "https://openagent3.xyz/skills/openspec/agent", "manifestUrl": "https://openagent3.xyz/skills/openspec/agent.json", "briefUrl": "https://openagent3.xyz/skills/openspec/agent.md" } } ``` ## Documentation ### OpenSpec — Spec-Driven Development OpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation. ### Setup # Install globally npm install -g @fission-ai/openspec@latest # Initialize in a project cd /path/to/project openspec init --tools claude # Update after CLI upgrade openspec update ### Core Workflow Each change follows: new → plan → apply → verify → archive ### 1. Start a Change # Create change folder with default schema openspec new change # With specific schema openspec new change --schema tdd-driven ### 2. Plan (Create Artifacts) Use the CLI instructions command to get enriched prompts for each artifact: # Get instructions for next artifact openspec instructions --change --json # Check progress openspec status --change --json Artifact sequence (spec-driven schema): proposal.md — Why and what (intent, scope, approach) specs/ — Requirements + scenarios (Given/When/Then) design.md — Technical approach and architecture decisions tasks.md — Implementation checklist with checkboxes ### 3. Implement Read tasks.md and work through items, marking [x] as complete. ### 4. Verify openspec validate --change --json Checks completeness, correctness, and coherence. ### 5. Archive openspec archive --yes Merges delta specs into main openspec/specs/ and moves change to archive. ### Agent Workflow (How to Use as an AI Agent) When the user asks to build/migrate/refactor something with OpenSpec: Check project state: openspec list --json # Active changes openspec list --specs --json # Current specs openspec schemas --json # Available schemas Create the change: openspec new change [--schema ] For each artifact, get instructions and create the file: openspec instructions --change --json openspec status --change --json Then write the artifact file to openspec/changes//. Implement tasks from tasks.md. Validate and archive: openspec validate --json openspec archive --yes ### CLI Quick Reference CommandPurposeopenspec list [--specs] [--json]List changes or specsopenspec show [--json]Show change/spec detailsopenspec status --change [--json]Artifact completion statusopenspec instructions [artifact] --change [--json]Get enriched creation instructionsopenspec validate [name] [--all] [--json]Validate changes/specsopenspec archive [--yes]Archive completed changeopenspec schemas [--json]List available schemasopenspec templates [--json]Show template pathsopenspec configView/modify settings Always use --json for programmatic/agent use. ### Custom Schemas Schemas define artifact sequences. Create custom ones for different workflows: # Fork built-in schema openspec schema fork spec-driven my-workflow # Create from scratch openspec schema init my-workflow # Validate openspec schema validate my-workflow Schema files live in openspec/schemas//schema.yaml with templates in templates/. For schema structure details, see references/schemas.md. ### Project Structure project/ ├── openspec/ │ ├── config.yaml # Project config (default schema, context, rules) │ ├── specs/ # Source of truth — current system behavior │ ├── changes/ # Active changes (one folder each) │ │ └── / │ │ ├── .openspec.yaml │ │ ├── proposal.md │ │ ├── specs/ # Delta specs (what's changing) │ │ ├── design.md │ │ └── tasks.md │ └── schemas/ # Custom schemas └── .claude/skills/ # Auto-generated Claude integration ### Spec Format Specs use RFC 2119 keywords (SHALL/MUST/SHOULD/MAY) with Given/When/Then scenarios: ### Requirement: User Authentication The system SHALL issue a JWT token upon successful login. #### Scenario: Valid credentials - GIVEN a user with valid credentials - WHEN the user submits login form - THEN a JWT token is returned ### Delta Specs Changes don't rewrite specs — they describe deltas (ADDED/MODIFIED/REMOVED) that merge into main specs on archive. ### Config openspec/config.yaml sets defaults: schema: spec-driven # or tdd-driven, rapid, custom context: | Tech stack: TypeScript, React, Node.js Testing: Jest rules: proposal: - Include rollback plan specs: - Use Given/When/Then format ## Trust - Source: tencent - Verification: Indexed source record - Publisher: jcorrego - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-30T16:55:37.338Z - Expires at: 2026-05-07T16:55:37.338Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/openspec) - [Send to Agent page](https://openagent3.xyz/skills/openspec/agent) - [JSON manifest](https://openagent3.xyz/skills/openspec/agent.json) - [Markdown brief](https://openagent3.xyz/skills/openspec/agent.md) - [Download page](https://openagent3.xyz/downloads/openspec)