Trellis Issue Creation FAQs

Question 1

Can I use this to update existing Trellis issues?

Accepted Answer

Yes, the skill has access to tools for getting, listing, and updating issues, allowing it to modify existing structures or add child issues to existing parents.

Question 2

Does it require manual input for acceptance criteria?

Accepted Answer

While it uses AI to generate success criteria based on requirements, it is designed to ask questions if requirements are genuinely ambiguous or if critical information is missing.

Question 3

What is the specific hierarchy used by this skill?

Accepted Answer

It follows a strict four-tier hierarchy: Project (top-level), Epic (work stream), Feature (implementable functionality), and Task (atomic unit of work, typically 1-2 hours).

Question 4

Does this skill automatically create a full task hierarchy?

Accepted Answer

No. To prevent over-engineering, the skill follows a 'Create Only Requested' rule. If you ask for a project, it creates the project and stops. You must explicitly ask to break down that project into epics or tasks.

Question 5

How does the skill know what technical details to include in an issue?

Accepted Answer

The skill performs a codebase search before creating any issues. It uses the current code as the source of truth to ensure the generated issues are relevant and technically accurate.

Trellis Issue Creation

Key Features

Use Cases

Trellis Issue Creation

Key Features

Use Cases