issue-creation

To create Trellis issues, this skill interprets natural-language requests to determine the correct issue type (Project, Epic, Feature, or Task). It reads type-specific guidelines and generates structured MCP entries while ensuring proper parent-child relationships across the project hierarchy.

The correct Trellis hierarchy includes Projects, Epics, Features, and Tasks with proper parent-child relationships. The skill enforces this structure by validating inputs against standard patterns and stopping after creating the identified issue type without automatic downstream creation.

No, you cannot create multiple issue levels simultaneously. The skill enforces a rule to stop immediately after creating the identified issue type. You must request downstream issues like epics or tasks in separate steps to maintain proper project structure and avoid misaligned hierarchies.

Trellis issue creation stops after making a project because the skill enforces a strict rule to halt execution after creating the identified issue type. This prevents automatic downstream creation, ensuring you validate each level's dependencies and structure before proceeding to the next.

The issue creation skill works with both new and existing Trellis projects by interpreting requests and ensuring proper parent-child relationships when applicable. It validates inputs against standard patterns to preserve consistent project structure across workflows, whether adding to existing projects or creating new ones.