pcli/.claude/commands/opsx/new.md at 22d5848e1a93f46b4c04eaa6b6260f7c34590cad

steve/pcli

Files

T

Steve Cliff 22d5848e1a feat: Add openspec-sync-specs and openspec-verify-change skills

- Introduced `openspec-sync-specs` skill to sync delta specs to main specs, allowing intelligent merging of requirements.
- Added `openspec-verify-change` skill to verify implementation against change artifacts, ensuring completeness, correctness, and coherence before archiving.

docs: Create CLAUDE.md for project guidance

- Added CLAUDE.md to provide an overview of the PCLI project, including build, test commands, architecture, and resource addition guidelines.

chore: Add new change and design documents for project filter in status command

- Created `.openspec.yaml`, `design.md`, `proposal.md`, and `tasks.md` for the `add-project-filter-to-status` change.
- Updated specs for CLI commands and status command to include project filtering functionality.

feat: Expand board included parsing in API client

- Added parsing for `labels`, `cardLabels`, and `cardMemberships` in the `GetBoard` response.
- Updated `ListCardsByBoard` to enrich card output with label names, enhancing usability in kanban sync workflows.

2026-02-18 21:27:02 +00:00

2.6 KiB

Raw Blame History

name, description, category, tags

name

description

tags

OPSX: New

Start a new change using the experimental artifact workflow (OPSX)

Workflow

workflow

artifacts

experimental

Start a new change using the experimental artifact-driven approach.

Input: The argument after /opsx:new is the change name (kebab-case), OR a description of what the user wants to build.

Steps

If no input provided, ask what they want to build

Use the AskUserQuestion tool (open-ended, no preset options) to ask:

"What change do you want to work on? Describe what you want to build or fix."

From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Determine the workflow schema

Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

Use a different schema only if the user mentions:
- A specific schema name → use --schema <name>
- "show workflows" or "what workflows" → run openspec schemas --json and let them choose
Otherwise: Omit --schema to use the default.
Create the change directory
```
openspec new change "<name>"
```
Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
Show the artifact status
```
openspec status --change "<name>"
```
This shows which artifacts need to be created and which are ready (dependencies satisfied).
Get instructions for the first artifact The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
```
openspec instructions <first-artifact-id> --change "<name>"
```
This outputs the template and context for creating the first artifact.
STOP and wait for user direction

Output

After completing the steps, summarize:

Change name and location
Schema/workflow being used and its artifact sequence
Current status (0/N artifacts complete)
The template for the first artifact
Prompt: "Ready to create the first artifact? Run /opsx:continue or just describe what this change is about and I'll draft it."

Guardrails

Do NOT create any artifacts yet - just show the instructions
Do NOT advance beyond showing the first artifact template
If the name is invalid (not kebab-case), ask for a valid name
If a change with that name already exists, suggest using /opsx:continue instead
Pass --schema if using a non-default workflow

2.6 KiB Raw Blame History

2.6 KiB

Raw Blame History