Initial commit
This commit is contained in:
27
commands/analyze-issue.md
Normal file
27
commands/analyze-issue.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
allowed-tools: Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(find:*), Bash(grep:*), Bash(wc:*), Bash(ls:*), Write, Read, MultiEdit,
|
||||
description: Analyze GitHub issue and generate technical specification
|
||||
---
|
||||
|
||||
# GitHub Issue Analysis and Technical Specification Generator
|
||||
|
||||
This template/script generates a technical specification for a GitHub issue with the following components:
|
||||
|
||||
## Key Components
|
||||
1. A bash script to fetch GitHub issue details
|
||||
2. A structured technical specification template with sections:
|
||||
- Issue Summary
|
||||
- Problem Statement
|
||||
- Technical Approach
|
||||
- Implementation Plan
|
||||
- Test Plan
|
||||
- Files to Modify/Create
|
||||
- Success Criteria
|
||||
- Out of Scope
|
||||
|
||||
## Principles
|
||||
- Test-Driven Development (TDD)
|
||||
- KISS (Keep It Simple, Stupid) approach
|
||||
- 300-line file size limit
|
||||
|
||||
The template is designed to provide a comprehensive, structured approach to analyzing and documenting technical issues from GitHub.
|
||||
1
commands/build-roadmap.md
Normal file
1
commands/build-roadmap.md
Normal file
@@ -0,0 +1 @@
|
||||
Use the roadmap-architect sub-agent to build comprehensive project roadmaps with strategic planning and timeline visualization. Parse $ARGUMENTS for scope and focus areas, analyze current project state from git history and documentation, define vision and strategic objectives, create structured roadmap with phases and dependencies, generate timeline visualization with Mermaid diagrams, document assumptions and risks, and create tracking mechanisms for progress monitoring.
|
||||
8
commands/create-coordination-files.md
Normal file
8
commands/create-coordination-files.md
Normal file
@@ -0,0 +1,8 @@
|
||||
---
|
||||
allowed-tools: Bash, Read, Write, Edit
|
||||
description: Generate coordination files for parallel workflow integration
|
||||
---
|
||||
|
||||
# Create Coordination Files
|
||||
|
||||
Generate coordination files for parallel workflow integration in agent workspace $ARGUMENTS. Read agent_context.yaml and validation_checklist.txt, calculate completion percentage, create status files and deployment plans in shared/coordination/ directory for seamless workflow integration.
|
||||
30
commands/use-agent.md
Normal file
30
commands/use-agent.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
allowed-tools: Task, Read, Glob, Bash
|
||||
description: Intelligently select and use appropriate sub-agent based on task requirements
|
||||
model: claude-sonnet-4-5-20250929
|
||||
---
|
||||
|
||||
# Use Agent
|
||||
|
||||
Analyze $ARGUMENTS to determine the most appropriate sub-agent from the .claude/agents directory and use it to handle the specified task.
|
||||
|
||||
$ARGUMENTS: [task description or agent:task format]
|
||||
|
||||
## Instructions - IMPORTANT: YOU MUST FOLLOW THESE INSTRUCTIONS EXACTLY IN THIS ORDER
|
||||
|
||||
1. Run !`ls -l ~/.claude/agents` to see available sub-agents.
|
||||
2. Parse $ARGUMENTS to identify task type, domain, and requirements
|
||||
3. If sub-agent is specified → Use specified sub-agent directly
|
||||
4. If format is "youtube-url", IMPORTANT: you must immediately send task to youtube-transcript-analyzer sub-agent.
|
||||
5. Otherwise, analyze task keywords to select appropriate sub-agent from the list of available sub-agents.
|
||||
6. Use the Task tool to spawn the selected sub-agent with appropriate parameters
|
||||
|
||||
## Context
|
||||
|
||||
Available sub-agents in @~/.claude/agents/:
|
||||
|
||||
## Output
|
||||
|
||||
- Selected sub-agent name and rationale
|
||||
- Task execution through the chosen sub-agent
|
||||
- Results from the sub-agent's processing
|
||||
9
commands/write-linear-issue.md
Normal file
9
commands/write-linear-issue.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
allowed-tools: Read, mcp__linear__create_issue, mcp__linear__get_project, mcp__linear__get_team, mcp__linear__get_user, mcp__linear__list_issue_labels, mcp__linear__list_issue_statuses, mcp__linear__list_projects, mcp__linear__list_teams, mcp__linear__list_users, mcp__linear__update_issue
|
||||
description: Create well-structured Linear issues for parallel development workflow
|
||||
model: claude-sonnet-4-5-20250929
|
||||
---
|
||||
|
||||
# Write Linear Issue
|
||||
|
||||
Create well-structured Linear issues optimized for parallel development workflow using Linear MCP tools. Use $ARGUMENTS for feature description and team identifier, fetch team and project context via mcp**linear**list_teams and related tools, structure issue with numbered tasks, acceptance criteria, and technical constraints following ai-docs/linear-issue-template.yaml format, then create issue via mcp**linear**create_issue and provide issue ID and URL.
|
||||
Reference in New Issue
Block a user