opsx-ff

Run /opsx-ff with a kebab-case change name or a description of what you want to build. The skill confirms the plan, lets you pick Sonnet or Opus for generation, then creates the proposal, specs, design, and tasks artifacts in dependency order.

It creates whatever the openspec schema's applyRequires list demands, typically proposal.md, delta spec files under specs/, design.md with a seed data section, and tasks.md with numbered implementation tasks. Optional artifacts are skipped when their skipWhen condition matches.

Generating proposal, specs, design, and tasks artifacts in one pass requires stronger reasoning than Haiku reliably provides. The skill stops immediately on Haiku and asks you to switch to Sonnet or Opus before proceeding.

Yes. The skill checks for context-brief.md, openspec/architecture ADRs, ARCHITECTURE.md, and FEATURES.md, but proceeds silently if none exist beyond standard ADRs. When present, their content drives the artifact decisions instead of invented details.

It shows the final openspec status and recommends next steps without auto-proceeding. The recommended follow-up is /opsx-apply to start implementing the tasks, or /opsx-plan-to-issues to create GitHub Issues for tracking.

When a change touches both declarative config and code, the skill offers to split it into a chain of specs linked by depends_on, since mixed specs historically exhaust the builder budget. A thin-glue exception allows mixed specs under roughly 20 lines of code across two files.