openspec-continue-change
Continue working on a change by creating the next artifact.
Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
-
If no change name provided, prompt for selection
Run
openspec list --jsonto get available changes sorted by most recently modified. Then use the AskUserQuestion tool to let the user select which change to work on.Present the top 3-4 most recently modified changes as options, showing:
- Change name
- Schema (from
schemafield if present, otherwise "spec-driven") - Status (e.g., "0/5 tasks", "complete", "no tasks")
- How recently it was modified (from
lastModifiedfield)
Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.
IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
More from sillsdev/fieldworks
atlassian-skills
Python utilities for Jira, Confluence, and Bitbucket integration. Provides issue management, search, workflows, page management, pull requests, commit history, and more. Use when users need to interact with Atlassian products like "create a Jira issue", "search Confluence pages", "create a pull request", "get commit history", or "update sprint status".
27powershell
>
19atlassian-readonly-skills
Read-only Python utilities for Jira, Confluence, and Bitbucket integration. Provides read access to issues, search, workflows, pages, pull requests, commit history, and more. Use when users need to query Atlassian products like "get a Jira issue", "search Confluence pages", "view pull request details", or "get commit history". This variant excludes all write operations for token efficiency and safety.
19review
Review changes for correctness, style, and risk; propose fixes or follow-ups.
17openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
17openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
16