openspec-new-change

Invoke the new-change flow without arguments; it auto-detects the most recent «Постановка ЗНИ» block in the session or a handoff file from the last 48 hours. It derives a kebab-case name and generates proposal, design, tasks, and spec artifacts in dependency order.

Pass the existing change name as an argument. If the change directory already exists, the skill skips scaffolding, reuses metadata from proposal.md when valid, and continues creating only the missing artifacts required before implementation.

Yes, the openspec CLI is required. The skill runs commands like openspec new change, openspec status, and openspec instructions to scaffold the change directory and determine the artifact build order.

When structural or semantic triggers fire and no architecture report exists, the skill pauses and delegates a design review to the architect agent, saving a report under reports/. You can consciously bypass it only by rerunning with the --skip-architect flag and a reason.

Slice decomposition is mandatory when the estimated work exceeds about five tasks. The architect agent adds a Slices section to design.md, and each slice gets exactly one acceptance task with a primary acceptance checklist in tasks.md.

The Metadata Gate collects the developer name and a one-phrase Russian description used in code comment markers. If a default developer is set in project.md, only the description draft is confirmed; otherwise the name is asked once and can be saved as default.