Implement OpenSpec change tasks by processing open and closed task files.
npx skills add https://github.com/moogah/emacs --skill opsx-apply-moogah
Please help me install this Agent Skill. Skill: opsx-apply Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-apply Command: npx skills add https://github.com/moogah/emacs --skill opsx-apply-moogah
Implement tasks from an OpenSpec change by coordinating the reading, evaluation, and application of task files generated from OpenSpec designs. This skill streamlines turning design work into concrete changes within a controlled task workflow, reducing manual coordination overhead.
Provide a change identifier or allow the system to infer it, then run the opsx-apply workflow to begin implementing tasks.
High-intent search queries and answers about installing and using this skill.
To implement OpenSpec change tasks, this skill processes files in openspec/changes/<name>/tasks/open and closed directories, reading design context and applying readiness rules to move tasks accordingly. It coordinates reading, evaluation, and application of task files generated from OpenSpec designs.
Task readiness validation works by applying status rules to open and closed task files, verifying alignment with the change's design artifacts, architecture, and specs. The system evaluates frontmatter and context to determine which tasks are ready, blocked, or completed.
Yes, you can use this to manage task status transitions for development automation. It provides guardrails and safe transitions between open and closed tasks, updating frontmatter to reflect completion while reporting progress throughout the implementation workflow.
When implementing tasks from an OpenSpec change, the system loads shared context from the change's design, architecture, specs, and proposals. It reads these artifacts into context to verify alignment with implementation tasks before applying readiness rules.
No, you do not need to manually specify the change identifier. You can provide a change identifier or allow the system to infer it, then run the workflow to begin implementing tasks from the OpenSpec change automatically.
OpenSpec tasks remain blocked when status rules and context validation determine they are not ready. The system checks alignment with design, architecture, specs, and proposals, and only moves tasks when readiness criteria are fully satisfied.
CatsofsufferingGenerate OpenSpec proposal, design, and task artifacts for implementation.
chuangkevinArchive completed openspec changes into openspec/changes/archive with status checks.
tenondecrpcAutomate OpenSpec change task implementation with status tracking and progress updates.
akaiholaExecute Playwright browser automation scripts for testing and interaction tasks.
