Workflow

The usual path is Create → Review → (Change) → Apply → Verify → Finish.

1. Create spec

Click Create spec. The AI reads the ticket summary and description and your repository, derives a short change name and writes the artifacts in dependency order: proposal, specs, design, tasks. The result is committed with the message <ISSUE-KEY> - <summary> and pushed to a new ai/* branch. A comment on the issue summarizes it, and the files appear as tabs in the panel.

If you are not happy with the whole direction, improve the ticket and click Recreate spec. This replaces the previous spec files in the panel.

2. Review and edit

Open each tab and read it. Click Edit to change an artifact in the rich-text editor, then save. Your edits are stored in Jira and are written back into the repository whenever the AI runs the next step, so they are never overwritten.

Editing is disabled while a job is running and after the spec has been applied or finished.

3. Change spec

For bigger adjustments, click Change spec and describe what should be different in plain language, for example "Also support SSO login and drop the migration task". The AI updates only the affected artifacts and keeps the rest. It does not touch code or tick tasks. The update is committed to the same branch.

4. Apply spec

Apply spec implements the pending tasks one by one and ticks them off in tasks.md. It then merges the delta specs into your main specs under openspec/specs/. Code, the ticked task list and the synced specs are committed to the same branch.

Apply runs without interaction. The AI does not stop to ask questions: it chooses the most reasonable interpretation, and reports blockers in its summary. Make sure the spec is clear before you apply.

5. Verify changes

The AI checks the implementation against the spec in three dimensions and posts a report as a Jira comment.

Dimension	Checks
Completeness	Are all tasks done and all requirements covered?
Correctness	Does the code match the requirements and scenarios?
Coherence	Does it follow the design and your code patterns?

Findings are labeled CRITICAL, WARNING or SUGGESTION, with file and line references where possible. The report ends with a verdict: Ready for archive or Fix before archiving.

6. Finish spec

Finish spec archives the change: openspec/changes/<name> moves to openspec/changes/archive/YYYY-MM-DD-<name>, after unsynced delta specs have been synced. Incomplete tasks do not block it and are reported as warnings. The files stay visible in the panel, and the status becomes Finished spec. To make another change, create a new spec.

Support

For help or to report issues, email support@smart-fusion.tech.

← Overview & setup Best practices →