openspec-ff-change

Create all OpenSpec framework artifacts for a new change in dependency order.

133|23|Updated Mar 23, 2020
One-click install
npx skills add https://github.com/aehrc/pathling --skill openspec-ff-change-aehrc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/aehrc/pathling/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/aehrc/pathling --skill openspec-ff-change-aehrc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of all necessary artifacts for implementing a new change within the OpenSpec framework, eliminating manual steps and ensuring a complete setup.

Core Features & Use Cases

  • Automated Artifact Generation: Creates all required artifacts for a given change in one go.
  • Dependency Management: Understands and creates artifacts in the correct dependency order.
  • Use Case: When starting a new feature development in OpenSpec, use this Skill to quickly scaffold all necessary configuration files, documentation templates, and code stubs, allowing developers to focus on implementation immediately.

Quick Start

Use the openspec-ff-change skill to create all artifacts for a new change named 'add-user-profile'.

Frequently Asked Questions about openspec-ff-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate artifact creation for a new change in OpenSpec?

You can automate artifact creation by providing a change name or description to this skill. It resolves dependencies and sequentially generates all required configuration files, documentation templates, and code stubs in one automated workflow.

What is the best way to scaffold OpenSpec configuration files and templates?

Scaffolding OpenSpec configuration files and templates is best handled by automating dependency resolution and sequential generation. This approach ensures all necessary artifacts for a new feature are created in the correct order before implementation begins.

Can I generate all development workflow artifacts for OpenSpec in one go?

Generating all development workflow artifacts in one go is supported by this skill's sequential artifact generation logic. It takes a user-provided change description and creates every required file, ensuring complete setup before you proceed to coding.

Do I need to manually resolve dependencies when creating OpenSpec change artifacts?

Manual dependency resolution is not required when creating OpenSpec change artifacts. The skill understands the dependency order and automatically creates the necessary scaffolding sequentially to ensure a complete and valid setup.

Why does my OpenSpec change implementation fail due to missing artifacts?

OpenSpec change implementation fails when required artifacts are missing because the dependency order was not followed. Automating artifact generation ensures all necessary configuration files and stubs are created before implementation proceeds.