Full-stack-skills openspec-apply

Implement tasks from the change using `/opsx:apply`, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".

install

source · Clone the upstream repo

git clone https://github.com/partme-ai/full-stack-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/partme-ai/full-stack-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/openspec-skills/openspec-apply" ~/.claude/skills/partme-ai-full-stack-skills-openspec-apply && rm -rf "$T"

manifest: skills/openspec-skills/openspec-apply/SKILL.md

OpenSpec Apply Skill

Use

/opsx:apply

to implement tasks from a change. The agent reads

tasks.md

, works through tasks one by one, writes code, creates files, runs tests as needed, and checks off completed items with

[x]

When to Use

All planning artifacts are complete and the user wants to implement.
The user says "implement", "apply", "start coding", "execute tasks".
Resuming implementation after an interruption.

Prerequisites

Planning artifacts complete — at minimum
```
tasks.md
```
exists (created via openspec-ff or openspec-continue).

Workflow

Start implementation
- ```
/opsx:apply
```
  — apply the current/inferred change.
- ```
/opsx:apply <change-name>
```
  — apply a specific change.
Read tasks
- The agent reads
```
tasks.md
```
  and identifies incomplete tasks (unchecked
```
[ ]
```
  items).
Work through tasks
- For each task: read relevant specs, design, and existing code; write code; create/modify files; run tests.
- Mark each task complete with
```
[x]
```
  in
```
tasks.md
```
  .
Handle issues
- If a task reveals that the design was wrong, edit the artifact (e.g.
```
design.md
```
  ) and continue.
- OpenSpec is fluid — updating artifacts during implementation is expected and encouraged.
Resume if interrupted
- Run
```
/opsx:apply
```
  again; it picks up where it left off based on checkbox state.

Outputs

Code changes (new files, modified files) implementing the tasks.
```
tasks.md
```
updated with
```
[x]
```
for completed tasks.

Next Steps

Use openspec-verify to validate implementation matches artifacts.
Use openspec-archive to archive the completed change.

Troubleshooting

"Change not found": Specify the change name:
```
/opsx:apply add-dark-mode
```
.
Tasks seem wrong: Edit
```
tasks.md
```
(or use
```
/opsx:continue
```
to regenerate) before applying.
Implementation diverges from design: Edit
```
design.md
```
or
```
specs/
```
as needed; OpenSpec is iterative.