@langadventurellc/task-trellis-mcp 1.3.2 → 1.3.3

package/dist/resources/basic-claude/agents/issue-verifier.md

@@ -1,154 +0,0 @@
----
-name: issue-verifier
-description: Verifies Trellis issues (projects, epics, features, tasks) against original requirements. Pass the original user requirements, the created issue details, and any additional context for evaluation of completeness, correctness, and appropriate scope.
-tools: Glob, Grep, LS, ExitPlanMode, Read, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__task-trellis__get_issue, mcp__task-trellis__list_issues
----
-
-# Issue Verifier Sub-Agent
-
-Evaluate created Trellis issues against original requirements to ensure completeness, correctness, and appropriate scope.
-
-## Goal
-
-Verify that a created issue (project, epic, feature, or task) accurately reflects the original user requirements without over-engineering or missing critical elements.
-
-## Input Requirements
-
-The calling agent should provide:
-
-- **Original Requirements**: The user's initial request or specifications
-- **Created Issue**: The issue ID or full issue details from Trellis
-- **Additional Context**: Any clarifications or decisions made during creation
-
-## Verification Process
-
-### 1. Parse Inputs
-
-Extract and analyze:
-
-- Original user requirements and constraints
-- Created issue details (title, description, acceptance criteria)
-- Any additional context provided
-
-### 2. Research Codebase Context
-
-**Investigate the existing system to validate appropriateness:**
-
-- **Search for similar implementations** to verify consistency
-- **Check architectural patterns** used in the codebase
-- **Identify existing utilities/libraries** that should be leveraged
-- **Verify integration points** mentioned are valid
-
-### 3. Completeness Check
-
-Verify the created issue includes all required elements:
-
-**For Projects:**
-
-- All functional requirements from user input are addressed
-- Technical architecture is specified
-- Integration points are defined
-- Acceptance criteria are measurable and complete
-
-**For Epics:**
-
-- Covers complete functional area
-- Clear scope boundaries
-- Logical grouping of related features
-
-**For Features:**
-
-- Specific user-facing capability defined
-- Clear acceptance criteria
-- Integration with other features specified
-
-**For Tasks:**
-
-- Implementable unit of work
-- Clear technical specifications
-- Dependencies identified
-
-### 4. Correctness Check
-
-Validate accuracy and appropriateness:
-
-- **Technical Accuracy**: Verify proposed solutions align with codebase patterns
-- **Requirement Alignment**: Ensure interpretation matches user intent
-- **Feasibility**: Confirm approach is technically viable
-- **Consistency**: Check alignment with existing system architecture
-
-### 5. Scope Assessment
-
-Evaluate for over-engineering:
-
-- **Compare scope to requirements**: Identify additions beyond user request
-- **Assess complexity**: Flag unnecessary complexity
-- **Check for premature optimization**: Identify optimizations not required
-- **Validate abstractions**: Ensure abstractions are justified by requirements
-
-**Note**: If user explicitly requested comprehensive or future-proofed solution, expanded scope is acceptable.
-
-### 6. Generate Evaluation Report
-
-## Output Format
-
-Return structured evaluation:
-
-```
-# Issue Verification Report
-
-## Issue Details
-- Type: [project/epic/feature/task]
-- ID: [issue-id]
-- Title: [issue-title]
-
-## Completeness Assessment
-✅ Complete | ⚠️ Partial | ❌ Incomplete
-
-**Required Elements:**
-- [Element]: [✅/❌] [Status/Comments]
-- [Element]: [✅/❌] [Status/Comments]
-
-**Missing Requirements:** (if any)
-- [Requirement not addressed]
-
-## Correctness Assessment
-✅ Correct | ⚠️ Issues Found | ❌ Major Problems
-
-**Findings:**
-- [Finding with specific details]
-
-**Codebase Alignment:**
-- [Pattern/Convention]: [Aligned/Misaligned - details]
-
-## Scope Assessment
-✅ Appropriate | ⚠️ Minor Over-engineering | ❌ Significant Over-engineering
-
-**Scope Analysis:**
-- User requested: [Summary of original scope]
-- Issue includes: [Summary of created scope]
-- Additional elements: [List any additions]
-- Justification: [Valid/Invalid - explanation]
-
-## Recommendations
-
-**Critical Issues:** (if any)
-- [Issue requiring immediate correction]
-
-**Suggested Improvements:** (if any)
-- [Non-critical improvement suggestion]
-
-## Overall Verdict
-[APPROVED / NEEDS REVISION / REJECTED]
-
-**Summary:**
-[Brief summary of the evaluation outcome]
-```
-
-## Rules
-
-- **Be objective**: Base assessments on requirements and codebase evidence
-- **Provide specifics**: Include concrete examples in findings
-- **Consider context**: Account for clarifications made during creation
-- **Focus on value**: Flag over-engineering only when it adds complexity without benefit
-- **Research thoroughly**: Use codebase search before claiming something doesn't exist

package/dist/resources/basic-claude/prompts/create-epics.md

@@ -1,204 +0,0 @@
----
-description: Break down a project into major epics by analyzing the project specification
----
-
-# Create Epics Command
-
-Break down a project into major epics using the Trellis task management system by analyzing the project specification and gathering additional requirements as needed. Do not attempt to create multiple epics in parallel. Do them sequentially one at a time.
-
-## Goal
-
-Analyze a project's comprehensive specification to create well-structured epics that represent major work streams, ensuring complete coverage of all project requirements and enabling effective feature decomposition.
-
-## Process
-
-### 1. Identify Target Project
-
-#### Input
-
-`$ARGUMENTS`
-
-#### Project Context
-
-The project ID may be:
-
-- Provided in `input` (e.g., "P-inventory-mgmt")
-- Known from previous conversation context
-- Specified along with additional instructions in `input`
-
-#### Instructions
-
-Retrieve the project using MCP `get_issue` to access its comprehensive description and requirements.
-
-### 2. Analyze Project Specification
-
-**Thoroughly analyze the project description to identify natural epic boundaries:**
-
-- **Use context7 MCP tool** to research architectural patterns and best practices
-- **Search codebase** for similar epic structures or patterns
-- Extract all functional requirements from the project description
-- Identify major technical components and systems
-- Consider cross-cutting concerns (security, testing, deployment, monitoring)
-- Group related functionality into cohesive work streams
-- Identify dependencies between work streams
-- Consider development phases and prerequisites
-- Note any specific instructions provided in `input`
-
-### 3. Gather Additional Information
-
-**Ask clarifying questions as needed to refine the epic structure:**
-
-Use this structured approach:
-
-- **Ask one question at a time** with specific options
-- **Focus on epic boundaries** - understand where one epic ends and another begins
-- **Identify component relationships** - how epics interact with each other
-- **Continue until complete** - don't stop until you have clear epic structure
-
-Key areas to clarify:
-
-- **Epic Boundaries**: Where does one epic end and another begin?
-- **Dependencies**: Which epics must complete before others can start?
-- **Technical Grouping**: Should technical concerns be separate epics or integrated?
-- **Phases**: Should there be phase-based epics (MVP, Enhancement, etc.)?
-- **Non-functional**: How to handle security, performance, monitoring as epics?
-
-**Example questioning approach:**
-
-```
-How should the authentication system be organized as an epic?
-Options:
-- A) Separate epic for all authentication (login, registration, password reset)
-- B) Integrate authentication into each functional epic
-- C) Split into multiple epics (core auth, advanced features, integrations)
-```
-
-Continue until the epic structure:
-
-- Covers all aspects of the project specification
-- Has clear boundaries and scope
-- Enables parallel development where possible
-- Supports logical feature breakdown
-
-### 4. Generate Epic Structure
-
-For each epic, create:
-
-- **Title**: Clear, descriptive name (3-5 words)
-- **Description**: Comprehensive explanation including:
-  - Purpose and goals
-  - Major components and deliverables
-  - **Detailed Acceptance Criteria**: Specific, measurable requirements that define epic completion, including:
-    - Functional deliverables with clear success metrics
-    - Integration requirements with other epics or external systems
-    - Performance and quality standards specific to this epic
-    - Security and compliance requirements
-    - User experience and usability criteria
-    - Testing and validation requirements
-  - Technical considerations
-  - Dependencies on other epics
-  - Estimated scale (number of features)
-  - **User Stories** - Key user scenarios this epic addresses
-  - **Non-functional Requirements** - Performance, security, scalability considerations specific to this epic
-
-### 5. Create Epics Using MCP
-
-For each epic, call the Task Trellis MCP `create_issue` tool:
-
-- `type`: Set to `"epic"`
-- `parent`: The project ID
-- `title`: Generated epic title
-- `status`: Set to `"open"` (default, ready to begin work) or `"draft"` unless specified
-- `prerequisites`: List of epic IDs that must complete first
-- `description`: Comprehensive epic description with all elements from step 4
-
-**For standalone epics**: Simply omit the `parent` parameter entirely.
-
-### 6. Verify Created Project
-
-Call the `issue-verifier` sub-agent to validate the created project:
-
-**Prepare verification inputs:**
-
-- Original specifications from `$ARGUMENTS`
-- Created issue ID(s) from the MCP response
-- Any additional context gathered during requirement gathering phase
-
-**Call the verifier:**
-
-```
-Verify the created project for completeness and correctness:
-- Original requirements: [Include the original $ARGUMENTS specifications]
-- Created issue ID(s): [issue-id from MCP response]
-- Additional context: [Include any clarifications, decisions, or requirements gathered during the interactive Q&A phase]
-```
-
-**Review verification results:**
-
-- If verdict is `APPROVED`: Proceed to output format
-- If verdict is `NEEDS REVISION`: Evaluate the feedback and, if applicable, update the project using MCP based on recommendations
-- If verdict is `REJECTED`: Evaluate the feedback and, if applicable, recreate the project addressing critical issues
-
-If you're not 100% sure of the correctness of the feedback, **STOP** and ask the user for clarification.
-
-### 7. Output Format
-
-After successful creation:
-
-```
-✅ Successfully created [N] epics for project "[Project Title]"
-
-📋 Created Epics:
-1. E-[id1]: [Epic 1 Title]
-   → Dependencies: none
-
-2. E-[id2]: [Epic 2 Title]
-   → Dependencies: E-[id1]
-
-3. E-[id3]: [Epic 3 Title]
-   → Dependencies: E-[id1], E-[id2]
-
-📊 Epic Summary:
-- Total Epics: [N]
-```
-
-## Simplicity Principles
-
-When creating epics, follow these guidelines:
-
-### Keep It Simple:
-
-- **No over-engineering** - Create only the epics needed for the project
-- **No extra features** - Don't add functionality that wasn't requested
-- **Choose straightforward approaches** - Simple epic structure over complex hierarchies
-- **Solve the actual problem** - Don't anticipate future requirements
-
-### Forbidden Patterns:
-
-- **NO premature optimization** - Don't optimize epic structure unless requested
-- **NO feature creep** - Stick to the specified project requirements
-- **NO complex dependencies** - Keep epic relationships simple and clear
-
-### Modular Architecture:
-
-- **Clear boundaries** - Each epic should have distinct, well-defined responsibilities
-- **Minimal coupling** - Epics should interact through clean interfaces, not internal dependencies
-- **High cohesion** - Related functionality should be grouped within the same epic
-- **Clean interfaces** - Define clear contracts between epics for data and functionality exchange
-
-## Question Guidelines
-
-Ask questions that:
-
-- **Clarify epic boundaries**: What functionality belongs together?
-- **Identify dependencies**: What must be built first?
-- **Consider team structure**: Can epics be worked on in parallel?
-- **Plan for phases**: MVP vs full implementation?
-- **Address non-functionals**: Where do performance/security requirements fit?
-
-<rules>
-  <critical>Use MCP tools for all operations (create_issue, get_issue, etc.)</critical>
-  <critical>Ask one question at a time with specific options</critical>
-  <critical>Continue asking questions until you have complete understanding of epic boundaries</critical>
-  <important>Epic descriptions must be detailed enough for feature creation</important>
-</rules>

package/dist/resources/basic-claude/prompts/create-features.md

@@ -1,199 +0,0 @@
----
-description: Break down an epic into specific features by analyzing the epic specification
----
-
-# Create Features Command
-
-Break down an epic into specific features using the Trellis task management system by analyzing the epic specification and gathering additional requirements as needed. Do not attempt to create multiple features in parallel. Do them sequentially one at a time.
-
-## Goal
-
-Analyze an epic's comprehensive specification to create well-structured features that represent implementable functionality, ensuring complete coverage of the epic's scope and enabling effective task decomposition.
-
-**IMPORTANT**: Features must include actual changes, implementations, or deliverables. Do not create features that are purely research tasks or analysis tasks without any tangible output. Since all features and tasks are executed independently without context from other features or tasks, purely analytical work provides no value.
-
-## Process
-
-### 1. Identify Context and Requirements
-
-#### Input
-
-`$ARGUMENTS`
-
-#### Context Determination
-
-The input may contain:
-
-- **Epic ID**: (e.g., "E-user-auth") - Create features within an epic hierarchy
-- **Feature Requirements**: Direct description of standalone functionality needed
-- **Mixed**: Epic ID plus additional feature specifications
-
-#### Instructions
-
-**For Hierarchical Features:**
-
-- Retrieve the epic using MCP `get_issue` to access its comprehensive description, requirements, and parent project context
-
-**For Standalone Features:**
-
-- Analyze the provided requirements directly
-- No parent context needed, focus on the specific functionality described
-
-### 2. Analyze Requirements
-
-**Thoroughly analyze the requirements (epic description OR standalone requirements) to identify natural feature boundaries:**
-
-- **Search codebase** for similar feature patterns or implementations
-- Extract all deliverables and components from the epic description
-- Review architecture diagrams and technical specifications
-- Analyze user stories to identify discrete user-facing functionality
-- Consider non-functional requirements that need specific implementation
-- Group related functionality into cohesive features
-- Identify dependencies between features
-- Note any specific instructions provided in `input`
-
-### 3. Gather Additional Information
-
-**Ask clarifying questions as needed to refine the feature structure:**
-
-Use this structured approach:
-
-- **Ask one question at a time** with specific options
-- **Focus on feature boundaries** - understand what constitutes a complete, testable feature
-- **Identify component relationships** - how features interact with each other
-- **Continue until complete** - don't stop until you have clear feature structure
-
-Key areas to clarify:
-
-- **Feature Boundaries**: What constitutes a complete, testable feature?
-- **Dependencies**: Which features must be implemented before others?
-- **Technical Approach**: How should complex functionality be divided?
-- **Testing Strategy**: How can features be tested independently?
-- **Integration Points**: Where do features interface with each other?
-
-**Example questioning approach:**
-
-```
-How should the user registration feature be scoped?
-Options:
-- A) Basic registration only (email, password, confirmation)
-- B) Full registration with profile setup and email verification
-- C) Registration with social login integration included
-```
-
-Continue until the feature structure:
-
-- Covers all aspects of the epic specification
-- Represents 6-20 tasks worth of work per feature
-- Has clear implementation boundaries
-- Enables independent development and testing
-
-### 4. Generate Feature Structure
-
-For each feature, create:
-
-- **Title**: Clear, specific name (3-5 words)
-- **Description**: Comprehensive explanation including:
-  - Purpose and functionality
-  - Key components to implement
-  - **Detailed Acceptance Criteria**: Specific, measurable requirements that define feature completion, including:
-    - Functional behavior with specific input/output expectations
-    - User interface requirements and interaction patterns
-    - Data validation and error handling criteria
-    - Integration points with other features or systems
-    - Performance benchmarks and response time requirements
-    - Security validation and access control requirements
-    - Browser/platform compatibility requirements
-    - Accessibility and usability standards
-  - Technical requirements
-  - Dependencies on other features
-  - **Implementation Guidance** - Technical approach and patterns to follow
-  - **Testing Requirements** - How to verify the feature works correctly
-  - **Security Considerations** - Input validation, authorization, data protection needs
-  - **Performance Requirements** - Response times, resource usage constraints
-
-**Feature Granularity Guidelines:**
-
-Each feature should be sized appropriately for task breakdown:
-
-- **1-2 hours per task** - When broken down, each task should be completable in 1-2 hours
-- **Independent implementation** - Features should be implementable without blocking other features
-- **Testable boundaries** - Features should have clear success criteria and testing strategies
-
-### 5. Create Features Using MCP
-
-For each feature, call the Task Trellis MCP `create_issue` tool:
-
-- `type`: Set to `"feature"`
-- `parent`: The epic ID (optional - omit for standalone features)
-- `title`: Generated feature title
-- `status`: Set to `"open"` (default, ready to begin work) or `"draft"` unless specified
-- `prerequisites`: List of feature IDs that must complete first
-- `description`: Comprehensive feature description with all elements from step 4
-
-**For standalone features**: Simply omit the `parent` parameter entirely.
-
-### 6. Verify Created Project
-
-Call the `issue-verifier` sub-agent to validate the created project:
-
-**Prepare verification inputs:**
-
-- Original specifications from `$ARGUMENTS`
-- Created issue ID(s) from the MCP response
-- Any additional context gathered during requirement gathering phase
-
-**Call the verifier:**
-
-```
-Verify the created project for completeness and correctness:
-- Original requirements: [Include the original $ARGUMENTS specifications]
-- Created issue ID(s): [issue-id from MCP response]
-- Additional context: [Include any clarifications, decisions, or requirements gathered during the interactive Q&A phase]
-```
-
-**Review verification results:**
-
-- If verdict is `APPROVED`: Proceed to output format
-- If verdict is `NEEDS REVISION`: Evaluate the feedback and, if applicable, update the project using MCP based on recommendations
-- If verdict is `REJECTED`: Evaluate the feedback and, if applicable, recreate the project addressing critical issues
-
-If you're not 100% sure of the correctness of the feedback, **STOP** and ask the user for clarification.
-
-### 7. Output Format
-
-After successful creation:
-
-```
-✅ Successfully created [N] features for epic "[Epic Title]"
-
-📋 Created Features:
-1. F-[id1]: [Feature 1 Title]
-   → Dependencies: none
-
-2. F-[id2]: [Feature 2 Title]
-   → Dependencies: F-[id1]
-
-3. F-[id3]: [Feature 3 Title]
-   → Dependencies: F-[id1], F-[id2]
-
-📊 Feature Summary:
-- Total Features: [N]
-```
-
-## Question Guidelines
-
-Ask questions that:
-
-- **Define feature scope**: What's included vs excluded?
-- **Clarify technical approach**: Specific technologies or patterns?
-- **Identify dependencies**: Build order and integration points?
-- **Consider testing**: How to verify feature completeness?
-
-<rules>
-  <critical>Use MCP tools for all operations (create_issue, get_issue, etc.)</critical>
-  <critical>Ask one question at a time with specific options</critical>
-  <critical>Continue asking questions until you have complete understanding of feature boundaries</critical>
-  <important>Feature descriptions must be detailed enough for task creation</important>
-  <important>Include implementation guidance and testing requirements</important>
-</rules>