This skill should be used when the user asks to create Trellis issues including "create a project", "create epics", "create features", "create tasks", "new project", "new epic", "new feature", "new task", "break down project into epics", "break down epic into features", "break down feature into tasks", "decompose project", "decompose epic", "decompose feature", or mentions creating any type of issue in Trellis.
Create issues in the Trellis task management system. This skill supports creating all issue types: projects, epics, features, and tasks.
Trellis uses a hierarchical issue structure:
Project -> Epic -> Feature -> Task
Each type can be created standalone or within its parent hierarchy.
Based on the user's request, determine which issue type to create:
| User Request | Issue Type | Reference |
|---|---|---|
| "create a project", "new project", "set up project management" |
| Project |
| project.md |
| "create epics", "break down project into epics", "decompose project" | Epic | epic.md |
| "create features", "break down epic into features", "decompose epic" | Feature | feature.md |
| "create tasks", "break down feature into tasks", "decompose feature" | Task | task.md |
You will be given a plan, parent issue, or specification describing what to create. Research has been done before you were invoked — your job is to verify that input against the current codebase, not to re-research from scratch.
Spot-check before creating issues:
When you find discrepancies:
The codebase is the source of truth.
STOP after creating the identified issue type. Do not automatically create child issues.
Do NOT continue to break down the hierarchy further. Each level of decomposition requires a separate user request. After creating issues, report what was created and wait for further instructions.
All issue types share these principles: