I am not sure if this is Junie-specific. Spec syncing does not work correctly (agent just moves files over) because the archive spec says:
If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>")
But there's no such skill/tool/instructions included. Junie then skips this step, and just copies the file over as-is. This means the specs keep the ## MODIFIED Requirements headers and openspec view shows 0 total requirements.
These are the included skills currently:
ls .junie/skills
Directory: C:\[...]\.junie\skills
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 09/05/2026 16:58 openspec-apply-change
d---- 09/05/2026 16:58 openspec-archive-change
d---- 09/05/2026 16:58 openspec-explore
d---- 09/05/2026 16:58 openspec-propose
Note: now that I'm reading the sync skill I see that it also doesn't give a spec template, only for the deltas. Maybe it could include something like:
**Main Spec Format Reference**
```markdown
# Capability Name Specification
## Purpose
Short description of the capability and why it exists.
## Requirements
### Requirement: Feature name
The system SHALL do something.
#### Scenario: Some scenario
- **WHEN** user does X
- **THEN** system does Y
#### Scenario: ...
```
I am not sure if this is Junie-specific. Spec syncing does not work correctly (agent just moves files over) because the archive spec says:
But there's no such skill/tool/instructions included. Junie then skips this step, and just copies the file over as-is. This means the specs keep the
## MODIFIED Requirementsheaders andopenspec viewshows 0 total requirements.These are the included skills currently:
Note: now that I'm reading the sync skill I see that it also doesn't give a spec template, only for the deltas. Maybe it could include something like: