Create Trellis Issues

Instructions

1. Identify the issue type the user wants to create based on their request
2. Validate the provided inputs against the current codebase (see below)
3. Read the appropriate type-specific file for detailed creation instructions:
   • For projects: Read project.md
   • For epics: Read epic.md
   • For features: Read feature.md
   • For tasks: Read task.md
4. Follow the detailed process in that file to create the issue(s)

Validate Inputs

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:

• Verify key references: Confirm 2-3 file paths, components, or patterns named in the input actually exist
• Compare against reality: The input may have been written before other work was completed — check whether assumed state still holds
• Identify actual gaps: Only create issues for work that genuinely needs to be done

When you find discrepancies:

• Minor (wrong path, renamed symbol): Adapt and continue
• Major (plan assumes missing state, work already done): STOP and alert the user

The codebase is the source of truth.

Critical Rule: Create Only the Requested Issue Type

STOP after creating the identified issue type. Do not automatically create child issues.

• If the user asks to "create a project" → Create the project, then STOP
• If the user asks to "create epics for project P-123" → Create the epics, then STOP
• If the user asks to "create features for epic E-456" → Create the features, then STOP
• If the user asks to "create tasks for feature F-789" → Create the tasks, then STOP

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.

Common Principles

All issue types share these principles:

• Create only what was requested - If asked to create a project, create the project only. Do not also create epics, features, or tasks unless explicitly asked.
• Default to coarser granularity - Prefer fewer, larger issues that are easier for AI agents to orchestrate. Don't create many tiny issues.
• Ask questions only when necessary - Only ask when requirements are genuinely ambiguous, critical information is missing, or decisions have significant irreversible consequences.
• Include acceptance criteria - All issues should have measurable success criteria.
• Keep it simple - Follow KISS, YAGNI principles. Don't over-engineer the structure.
• Create sequentially - When creating multiple issues, do them one at a time, not in parallel.