sequential-execution
Sequential Execution
Execute tasks in order when dependencies exist between steps.
When to Use
Use sequential execution when:
- Tasks have dependencies (Task B needs Task A's output)
- Order matters for correctness
- Tasks modify shared state or files
- Workflow has clear sequential stages (e.g., commit → push → PR)
- Later tasks need results from earlier tasks
Parameters
- tasks: Ordered list of task descriptions
- dependencies: Map of task dependencies (which tasks depend on which outputs)
More from squirrel289/pax
resolve-pr-comments
Workflow skill for addressing and resolving pull request review comments systematically
11gh-pr-review
Interact with GitHub pull requests for review, comment management, and merge operations
10process-pr
End-to-end workflow for processing pull requests from review to merge
10copilot-pull-request
Skill for managing GitHub pull requests and issues using Copilot's built-in PR/issue APIs. Provides structured, agent-native operations for review, comment, resolve, and merge workflows.
10pull-request-tool
Unified skill for managing GitHub pull requests and issues. Uses Copilot's native PR/issue APIs when available, and falls back to gh-pr-review CLI otherwise. Ensures maximum compatibility and agent-native features.
10parallel-execution
CRITICAL skill for executing multiple runSubagent calls in a SINGLE function_calls block for true parallelism. Essential for efficient multi-task workflows, subagent coordination, and maximizing throughput.
10