Create Issues

Use act-create-issues to turn an approved Spec into independently executable Work Items after you approve the proposed breakdown.

A Work Item is a small implementation task created from a Spec, with context, acceptance criteria, dependencies, and verification steps.

When to use it

Use this skill after the Spec has been reviewed and is ready to break into implementation tasks. For non-trivial work, refine the Spec first with act-refine-spec.

If the Spec still has Blocking Questions, the agent stops before proposing Work Items. If open questions affect boundaries, dependencies, acceptance criteria, or scope, it asks only about those questions first.

Use act-create-issues-flutter when the project or task is Flutter/Dart. It creates Flutter/Dart vertical-slice Work Items with UX, state, and testing expectations carried forward.

Invoke it

General work

/act-create-issues <path/to/spec.md or GitHub issue>

Flutter work

/act-create-issues-flutter <path/to/spec.md or GitHub issue>

Proposal before writing

The agent always pauses before writing Work Items. It first shows a numbered proposal like this:

**1. Account deletion request**
- Scope: Add the account deletion command and confirmation flow.
- Blocked by: None
- Covers: User Stories 1; Requirements 1-2; Testing Strategy 1; Interview Ledger L1

**2. Deletion failure handling**
- Scope: Add retry and user-visible error behavior for failed deletion requests.
- Blocked by: 1
- Covers: Requirements 3-4; Testing Strategy 2; Interview Ledger L2
- Blocking decisions: Exact support contact copy is unresolved.

Review whether any Work Items are too coarse or too fine, should be combined or split, or have the wrong dependencies. The agent writes Work Items only after you approve the proposal.

What it writes

• Work Items in the same storage location as their parent Spec.

Each Work Item includes the approved scope, acceptance criteria, traceability, and dependency information:

## What to build
Add the account deletion command and confirmation flow.

## Acceptance criteria
- [ ] Users can request account deletion from settings.
- [ ] The UI requires explicit confirmation before deletion starts.
- [ ] Automated tests cover the confirmation flow.

## Covers
- User Stories: 1
- Requirements: 1-2
- Interview Ledger: L1

## Blocked by
None - ready to start

Covers links the Work Item back to the Spec and Interview Ledger. Blocked by lists prerequisite Work Items. Blocking decisions is added only when an unresolved decision must be answered before implementation.

Storage follows .act/config.yaml; see Project Setup for local Markdown and GitHub storage behavior.

After writing, the agent reports the created Work Item references and the next act-implement <Work Item reference> commands. It does not invoke implementation automatically.

Flutter/Dart Work Items

Use act-create-issues-flutter when the project or task is Flutter/Dart. It prefers vertical Flutter slices through UI, state, services/data, and tests instead of horizontal slices such as all models, then all providers, then all screens.

For user-facing work, it carries forward visible behavior, user-visible states, navigation boundaries, accessibility/responsive behavior, platform constraints, and the expected unit/widget/robot testing split.

Review before continuing

Check that each Work Item is independently executable, correctly scoped, ordered by real dependencies, and has clear acceptance criteria. Then run act-implement on one Work Item at a time.