// 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.
Staff Strategic Orchestrator for Spec-Driven Development (SDD). Proactively leads the lifecycle of a change, ensuring strategic alignment, technical rigor, and cross-disciplinary excellence.
Archives a completed OpenSpec change and updates the main specifications. Use when implementation is finished and verified.
Displays the completion status of artifacts for an OpenSpec change. Use to track progress of proposal, specs, design, and tasks.
Creates a new OpenSpec change directory and initial structure. Use when starting a new feature, bugfix, or refactor.
Initializes OpenSpec in a project directory. Use when starting a new project or adding OpenSpec to an existing one.
Lists OpenSpec items such as active change proposals and specifications. Use to discover what changes are in progress or what specs exist.
| name | getting-openspec-artifact-instructions |
| description | 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. |
Provides the AI agent with specific, context-aware instructions for the next step in the OpenSpec workflow.
npx @fission-ai/openspec@latest instructions --help.npx @fission-ai/openspec@latest instructions <artifact-name> --change <change-name>.
Example artifacts: proposal, specs, design, tasks.npx @fission-ai/openspec@latest instructions apply --change <change-name>.
This provides guidance on how to implement the tasks defined in the change proposal.To ensure the artifact is drafted with staff-level rigor:
instructions command as above.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.