# Create Tasks

> Create GitHub issues from a feature plan or PRD -- automatically determines single issue vs epic + task issues. Use after /prd or /plan-feature to push tasks to GitHub, or whenever the user wants to create structured issue(s) for a feature.

- **Type:** Skill
- **Install:** `agentstack add skill-makigjuro-cloudstack-ai-plugins-create-tasks`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [makigjuro](https://agentstack.voostack.com/s/makigjuro)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [makigjuro](https://github.com/makigjuro)
- **Source:** https://github.com/makigjuro/cloudstack-ai-plugins/tree/main/plugins/dev-workflow/skills/create-tasks
- **Website:** https://github.com/makigjuro/cloudstack-ai-plugins#quick-start

## Install

```sh
agentstack add skill-makigjuro-cloudstack-ai-plugins-create-tasks
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Create GitHub Tasks

Analyze a feature plan or PRD and create the appropriate GitHub issue structure. **Automatically decides** whether to create a single issue or an epic with multiple task issues based on scope and complexity.

## Configuration

Read `cloudstack.json` from the project root at the start of execution. Extract relevant fields:
- `REPO_OWNER` / `REPO_NAME` = `repository.owner` / `repository.name` (default: detect from `git remote -v`)

If `cloudstack.json` does not exist, auto-detect by parsing the GitHub remote URL:
```bash
git remote get-url origin | sed -E 's|.*github\.com[:/]([^/]+)/([^/.]+).*|\1 \2|'
```

## Arguments

- `{prd-path}` -- Path to PRD file (optional, will search `docs/prd/` or use conversation context)
- `--dry-run` -- Show what would be created without actually creating issues
- `--epic-only` -- Create only the epic issue, not individual tasks
- `--no-epic` -- Create only task issues, no parent epic

## Decision Logic: Single vs Multiple Issues

**Create a SINGLE issue when:**
- Feature has  3 implementation tasks
- Tasks span multiple services or layers
- A PRD exists with structured sections
- Tasks could be assigned to different people or done in separate PRs
- `--epic-only` or `--no-epic` flags override this logic

## Process

### Step 1: Find the Plan

1. If path provided, read that file
2. Else search `docs/prd/*.md` for most recent PRD
3. Else look for feature plan in conversation context
4. If nothing found, ask user to describe the feature or run `/plan-feature` or `/prd` first

### Step 2: Parse & Classify

Extract from the plan:
- **Title**: Feature name
- **Summary**: Description
- **Acceptance Criteria**: All AC items
- **Tasks**: Implementation tasks grouped by layer
- **Out of Scope**: Exclusions
- **Labels**: Derive from affected services (see Label Mapping below)

Apply the decision logic above to determine: **single issue** or **epic + tasks**.

### Step 3: Present Plan for Approval

Show the user what will be created:

```
## Issue Creation Plan

Mode: {Single Issue | Epic + N Task Issues}
Reason: {brief explanation of why this mode was chosen}

### {Single Issue title OR Epic title}
Labels: {labels}

### Tasks ({count})
1. {task description}
2. {task description}
...

Create? [Yes / Modify / Cancel]
```

### Step 4a: Single Issue Path

Create one issue with all tasks as a checklist using MCP:

```
mcp__github-mcp-server__create_issue(
  owner: "{REPO_OWNER}",
  repo: "{REPO_NAME}",
  title: "{Feature Title}",
  labels: ["{labels}"],
  body: "..."
)
```

Issue body format:

```markdown
## Summary
{description}

## Acceptance Criteria
- [ ] AC1: ...
- [ ] AC2: ...

## Implementation Tasks

### Domain
- [ ] {task}

### Application
- [ ] {task}

### Infrastructure
- [ ] {task}

### Endpoints
- [ ] {task}

### Frontend
- [ ] {task}

### Tests
- [ ] {task}

## Out of Scope
- {exclusions}

---
Generated with [Claude Code](https://claude.com/claude-code)
```

Only include layer sections that have tasks. Skip empty sections.

### Step 4b: Epic + Tasks Path

**Create the epic** using MCP:

```
mcp__github-mcp-server__create_issue(
  owner: "{REPO_OWNER}",
  repo: "{REPO_NAME}",
  title: "Epic: {Feature Title}",
  labels: ["epic", "feature", "{labels}"],
  body: "..."
)
```

Epic body format:

```markdown
## Summary
{summary}

## Acceptance Criteria
{all AC items as checkboxes}

## Task Issues

## Out of Scope
{exclusions}

## References
- PRD: {prd-path if applicable}

---
Generated with [Claude Code](https://claude.com/claude-code)
```

**Create each task issue** using MCP:

```
mcp__github-mcp-server__create_issue(
  owner: "{REPO_OWNER}",
  repo: "{REPO_NAME}",
  title: "[{Layer}] {Task Title}",
  labels: ["{layer-label}", "{service-labels}"],
  body: "..."
)
```

Task body format:

```markdown
## Parent Epic
#{epic-number}

## Task
{task description}

## Acceptance Criteria
{relevant AC items}

## Files to Modify
- `{file path}`

## Implementation Notes
{hints from PRD}

---
Generated with [Claude Code](https://claude.com/claude-code)
```

**Update epic with task links:**

```
mcp__github-mcp-server__update_issue(
  owner: "{REPO_OWNER}",
  repo: "{REPO_NAME}",
  issue_number: {epic-number},
  body: "{updated body with - [ ] #{taskN} -- {title} links}"
)
```

## Label Mapping

| Layer/Service | Labels |
|---------------|--------|
| Domain | `domain`, `backend` |
| Application | `application`, `backend` |
| Infrastructure | `infrastructure`, `backend` |
| Endpoints | `api`, `backend` |
| Frontend | `frontend` |
| Tests | `testing` |
| Helm/Terraform | `infrastructure`, `devops` |

General labels:
- `feature` for new functionality
- `enhancement` for improvements
- `bug` for defects

Add service-specific labels based on the services defined in `cloudstack.json` or discovered in the project.

## Task Title Conventions

Keep titles under 70 characters. Use `[Layer]` prefix for multi-issue mode:

| Description | Title |
|-------------|-------|
| "Add user entity to domain" | `[Domain] Add user entity` |
| "Create API endpoint for orders" | `[Endpoints] Add order creation endpoint` |

## Grouping Strategy

Group related tasks into single issues when:
- They modify the same file
- They're logically atomic (must be done together)
- They're trivial (< 10 lines each)

Split into separate issues when:
- Tasks can be done independently
- Different reviewers might handle them
- They touch different services

## Output Format

### Single Issue Output
```markdown
## Issue Created

- #{number}: {title}
  URL: {url}

## Next Steps
Run `/start-work #{number}` to begin implementation.
```

### Epic + Tasks Output
```markdown
## Issues Created

### Epic
- #{number}: {title} -- {url}

### Tasks ({count})
| # | Issue | Title | Labels |
|---|-------|-------|--------|
| 1 | #{n1} | {title1} | {labels} |
| 2 | #{n2} | {title2} | {labels} |

## Next Steps
1. Run `/start-work #{first-task}` to begin implementation
2. Close tasks as completed; epic tracks overall progress
```

## Error Handling

- **gh not authenticated**: Prompt user to run `gh auth login`
- **Label doesn't exist**: Create label or skip with warning
- **Rate limit**: Pause and retry with backoff
- **Partial failure**: Report which issues were created, which failed

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [makigjuro](https://github.com/makigjuro)
- **Source:** [makigjuro/cloudstack-ai-plugins](https://github.com/makigjuro/cloudstack-ai-plugins)
- **License:** MIT
- **Homepage:** https://github.com/makigjuro/cloudstack-ai-plugins#quick-start

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-makigjuro-cloudstack-ai-plugins-create-tasks
- Seller: https://agentstack.voostack.com/s/makigjuro
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.