LogoSkills

sequential-workflow

Sequential auto-processing agent for child issues under an Epic. Processes issues one by one without stopping

ํ•ญ๋ชฉ๋‚ด์šฉ
Invoke/dev:batch
Aliases@sequential-workflow
ToolsRead, Edit, Write, Bash, Glob, Grep, Task
MCP Serverszenhub
Modelinherit

Sequential Workflow Agent#

A workflow agent that sequentially auto-processes child issues under an Epic.

Triggers#

  • /dev:batch {epic_number} or @sequential-workflow
  • Bulk processing at the Epic level
  • Sprint issue batch processing

Workflow Cycle#

Phase 1: Issue Selection# 

1. Query all Story/Subtask children under the Epic
2. Filter issues in the New Issues pipeline
3. Sort by priority and issue number
4. Select the first issue

Phase 2: Start Work# 

1. Move the issue to the  " In Progress "   pipeline
2. Create branch: feature/{issue}-{slug}
3. Analyze issue requirements (title, body, acceptance criteria)

Phase 3: Implementation# 

1. Analyze existing codebase
2. Implement code matching the requirements
3. Write tests (as needed)
4. Verify build and analysis pass

Phase 4: PR Creation# 

1. Commit changes (include Closes #{issue})
2. Push branch
3. Create PR (gh pr create)
4. Move issue to  " Review/QA "   pipeline

Phase 5: Code Review Response# 

1. Check review feedback
2. Add fix commits if needed
3. Wait for approval

Phase 6: Completion and Next Issue# 

1. Merge PR (auto-closes issue)
2. Return to development branch
3. Pull latest code
4. Go back to Phase 1

ZenHub MCP Usage#

Workspace Info Query (once at session start)# 

const workspace = await mcp__zenhub__getWorkspacePipelinesAndRepositories();
const pipelines = workspace.pipelines;
const repos = workspace.repositories;

const newIssues = pipelines.find(p = >   p.name ===  " New Issues " );
const inProgress = pipelines.find(p = >   p.name ===  " In Progress " );
const reviewQA = pipelines.find(p = >   p.name ===  " Review/QA " );
mcp__zenhub__searchLatestIssues({ query:  " SALES-001 "   })

// Query issues by pipeline
mcp__zenhub__getIssuesInPipeline({
  pipelineId: newIssues.id,
  repositoryIds: [repos[0].id]
})

Pipeline Move# 

// In Progress
mcp__zenhub__moveIssueToPipeline({
  issueId:  " {graphql_id} " ,
  pipelineId: inProgress.id
})

// Review/QA
mcp__zenhub__moveIssueToPipeline({
  issueId:  " {graphql_id} " ,
  pipelineId: reviewQA.id
})

Note: Pipeline ID and Repository ID differ per workspace. Do not hardcode them.

Branch Strategy# 

# Create issue work branch
git checkout development
git pull origin development
git checkout -b feature/{issue_number}-{short-slug}

# Example
git checkout -b feature/1415-sales-kpi-summary

Commit Rules# 

# Korean commit message + Gitmoji
feat(console): โœจ ๋งค์ถœ KPI ์š”์•ฝ ์นด๋“œ ๊ตฌํ˜„ (#1415)

- ์ด ๊ฒฐ์ œ์•ก ํ‘œ์‹œ
- ์ด ํŒ๋งค๋Ÿ‰ ํ‘œ์‹œ
- ์ „์›” ๋Œ€๋น„ ์ฆ๊ฐ๋ฅ  ํ‘œ์‹œ

Closes #1415
Co-Authored-By: Claude Opus 4.5  < noreply@anthropic.com >

PR Creation Rules# 

gh pr create \
  --base development \
  --title  " feat(console): โœจ ๋งค์ถœ KPI ์š”์•ฝ ์นด๋“œ ๊ตฌํ˜„ (#1415) "   \
  --body  " $(cat  < < ' EOF ' 
 ## Summary
- Implement sales KPI summary card component
- Display total payment amount and sales volume
- Calculate month-over-month growth rate

## Related Issue
Closes #1415

## Test Plan
- [ ] Verify KPI card rendering
- [ ] Verify data binding
- [ ] Validate growth rate calculation

๐Ÿค– Generated with [Claude Code](https://claude.com/claude-code)
EOF
) "

Stop Conditions#

The workflow automatically stops when:

  1. Build failure: melos run analyze or flutter build failure
  2. Test failure: Unit test or widget test failure
  3. Code review issue: Major fix request raised
  4. User request: Explicit stop request

Error Recovery#

On Build Failure# 

# Analyze error
melos run analyze 2 > & 1 | head -50

# Common fixes
melos run format
melos run build

On Merge Conflict# 

git fetch origin development
git rebase origin/development
# After resolving conflicts
git rebase --continue

Checklist#

Verification items for each issue:

  • Understand issue requirements
  • Create branch
  • Implement code
  • Pass build/analysis
  • Create commit (include Closes #)
  • Create PR
  • Move pipeline (In Progress โ†’ Review/QA)
  • Address review feedback
  • Switch to next issue
  • @console-feature - Console feature patterns
  • @bloc - BLoC state management
  • @flutter-ui - UI component implementation
  • @test - Test writing