agentsclimarketplace

Getting openspec artifact instructions

Skill yu-iskw/openspec-skills/skills/getting-openspec-artifact-instructions

Agent Skills to effectively utilize OpenSpec

Install
npx -y skills add yu-iskw/openspec-skills --skill getting-openspec-artifact-instructions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Outputs enriched instructions for creating an artifact or applying tasks for an OpenSpec change. Use when the agent needs guidance on how to write a spec, design, or implement tasks.

SKILL.md

1.8 KB, 343 tokens by cl100k_base, as published. Nobody here has run it

Getting OpenSpec Artifact Instructions

Purpose

Provides the AI agent with specific, context-aware instructions for the next step in the OpenSpec workflow.

1. Safety & Verification

  1. Check Help: Run npx @fission-ai/openspec@latest instructions --help.

2. Common Workflows

Workflow: Get Instructions for a Specific Artifact

  1. Run npx @fission-ai/openspec@latest instructions <artifact-name> --change <change-name>. Example artifacts: proposal, specs, design, tasks.

Workflow: Get Implementation Instructions

  1. Run npx @fission-ai/openspec@latest instructions apply --change <change-name>. This provides guidance on how to implement the tasks defined in the change proposal.

Workflow: Get Instructions with Staff Context

To ensure the artifact is drafted with staff-level rigor:

  1. Run the standard instructions command as above.
  2. Enrichment: Supplement the CLI output with the following "Staff Context" questions:
    • "How does this artifact address the long-term architectural health of the project?"
    • "What are the cross-disciplinary implications (UX, Performance, Security) for this specific artifact?"
    • "Can we simplify this design to improve ROI without compromising core requirements?"

3. Examples

Example: Get Instructions for Writing Specs

Command: npx @fission-ai/openspec@latest instructions specs --change my-feature Expected Output: Detailed guidance on the structure and content expected for the specifications of my-feature.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.