Prompt file imported from HillPhelmuth/AgenticRpg (.github/prompts/create-tasks.prompt.md). Fill in {{context}} before use. Copyright stays with the author.

Create Project Tasks - Tactical Execution Prompt

Name: create-tasks
Author: HillPhelmuth

Purpose

This prompt guides GitHub Copilot through creating a comprehensive TASKS.md document that breaks down a project plan into actionable implementation tasks.

Instructions to Copilot

You are tasked with creating a tactical implementation plan based on an existing strategic project plan. The project has a PLANNING.md file that defines the vision, architecture, and roadmap.

Before starting, verify that PLANNING.md exists in the project. If it doesn't exist, inform the user that this file is required and cannot proceed with creating tasks.

Your Goal

Create a comprehensive TASKS.md file in the project root that provides:

Actionable, specific implementation tasks
Logical task organization and sequencing
Clear acceptance criteria for each task
Progress tracking with checkboxes

Project Context

Additional Context (Optional): {{context}}

TASKS.md Structure

Create a TASKS.md file with the following sections:

1. Initial Setup & Research

Environment configuration and foundational tasks:

Development environment setup
Install required tools and dependencies
Configure version control and branching strategy
Research and prototype key technologies
Set up development database/services

2. Architecture & Design

Design artifacts before coding begins:

Create system architecture diagrams
Define data models and schemas
Design API contracts and interfaces
Create component interaction diagrams
Document security architecture

3. Core Components Development

Implementation tasks for each component identified in PLANNING.md:

4. Integration & Configuration

Connect components and configure the system:

Integrate Component A with Component B
Configure environment variables
Set up configuration management
Implement logging and monitoring
Configure external service connections

5. Azure Service Integration (if applicable)

Set up and integrate cloud resources:

Provision Azure resources
Configure authentication and authorization
Set up managed identities
Implement Azure service connections
Configure monitoring and alerts

6. Testing & Quality Assurance

Comprehensive testing strategy:

Write integration tests
Write end-to-end tests
Perform load/performance testing
Security testing and vulnerability scans
Verify all requirements met

7. Documentation

Create user and developer documentation:

Write README with setup instructions
Document API endpoints and usage
Create architecture documentation
Write user guides
Document troubleshooting procedures

8. Deployment & Release

Prepare for production deployment:

9. Phase 2+ Features (Future Work)

Advanced features from later phases:

[Feature from Phase 2]
[Feature from Phase 3]
[Additional enhancements]

10. Discovered During Work

Dynamic section for emergent tasks:

[Tasks discovered during implementation]

How to Use This Prompt

Creating Tasks from Existing Plan:

I have PLANNING.md ready. Please create TASKS.md.

Expected actions:
1. Verify that PLANNING.md exists
2. Read and analyze the PLANNING.md file
3. Extract components, phases, and requirements
4. Create TASKS.md with all sections and specific tasks
5. Organize tasks in logical implementation order
6. Review the task list with me

Creating Tasks with Specific Focus:

Create TASKS.md based on PLANNING.md, focusing on [specific area or phase].

Expected actions:
1. Verify PLANNING.md exists
2. Read the planning document
3. Create comprehensive TASKS.md
4. Give extra detail to the specified focus area
5. Ensure dependencies are clear

Task Writing Guidelines

Each Task Should:

✅ Be specific and actionable (verb + noun + context)
✅ Have clear acceptance criteria
✅ Be small enough to complete in one session (2-8 hours)
✅ Have obvious dependencies identified
✅ Include testing requirements where applicable

Task Format Examples:

Good Tasks:

Implement user authentication using Azure AD B2C with JWT validation
Create REST API endpoint for feedback submission with JSON schema validation
Write unit tests for sentiment analysis service achieving >80% coverage

Poor Tasks:

Build the backend (too vague)
Make it work (no specific outcome)
Fix bugs (not specific enough)

Task Organization:

✅ Group related tasks together
✅ Order tasks by dependency (prerequisites first)
✅ Separate MVP tasks from enhancement tasks
✅ Use sub-sections for major components
✅ Include checkboxes for progress tracking

Example Output

User: "I have PLANNING.md for a customer feedback analysis system. Create TASKS.md."

Expected Copilot Response:

"I'll create a comprehensive task list based on your PLANNING.md. Let me first verify the file exists and review the plan..."

[Reads PLANNING.md]

"I've reviewed your planning document. I can see:

3 main components: Feedback API, Analysis Service, Dashboard
Azure AI Language for sentiment analysis
Cosmos DB for storage
3-phase roadmap

Creating TASKS.md now with tasks organized by setup, design, component development, integration, testing, and deployment..."

[Creates detailed TASKS.md]

"I've created TASKS.md with 47 specific tasks organized into logical sections:

Initial Setup: 6 tasks for environment and tools
Architecture & Design: 5 tasks for diagrams and data models
Core Components: 18 tasks across 3 components
Integration: 8 tasks for connecting services
Azure Integration: 5 tasks for cloud setup
Testing: 6 tasks for comprehensive QA
Documentation: 4 tasks
Deployment: 5 tasks for CI/CD and production

Phase 2+ features are captured but not detailed yet. Ready to begin implementation using build.prompt.md, or would you like to review and adjust any tasks first?"

If PLANNING.md doesn't exist:

"I cannot create TASKS.md because PLANNING.md is missing. PLANNING.md is required to understand:

What components need to be built
The technical architecture and approach
The phased roadmap and priorities

Please create PLANNING.md first using create-plan.prompt.md or manually using the template in samples/templates/. Once PLANNING.md exists, I can generate a comprehensive task list."

Best Practices

Task Creation

✅ Base tasks directly on components in PLANNING.md
✅ Break large tasks into smaller sub-tasks
✅ Include testing tasks for each component
✅ Don't forget documentation and deployment tasks
✅ Capture Phase 2+ features but don't detail them yet

Organization

✅ Group by logical workflow (setup → design → build → test → deploy)
✅ Within each group, order by dependency
✅ Use clear section headers
✅ Number tasks if helpful for reference

Clarity

✅ Use action verbs (implement, create, configure, test, deploy)
✅ Be specific about what "done" looks like
✅ Include relevant technology names
✅ Reference specific files or components when known

Azure Projects (when applicable)

✅ Include Azure resource provisioning tasks
✅ Add tasks for authentication setup
✅ Include monitoring and logging configuration
✅ Consider cost optimization tasks
✅ Plan for CI/CD with Azure DevOps or GitHub Actions

Troubleshooting

If PLANNING.md doesn't exist:

Stop and inform the user
Direct them to create PLANNING.md first
Do not attempt to create PLANNING.md yourself

If PLANNING.md is too vague:

Ask user to clarify specific sections
Suggest updating PLANNING.md before creating tasks
Make reasonable assumptions but document them

If task list becomes too large:

Focus on Phase 1/MVP tasks in detail
Summarize Phase 2+ tasks at high level
Suggest breaking into multiple epics or sprints

If dependencies are complex:

Create a dependency section at the top
Use task numbering for cross-referencing
Consider creating a task dependency diagram

Success Criteria

A good TASKS.md document:

✅ Translates all PLANNING.md components into concrete tasks
✅ Provides clear, actionable items that can be started immediately
✅ Includes all aspects: setup, development, testing, documentation, deployment
✅ Has tasks small enough to complete in one session
✅ Shows clear progression and dependencies
✅ Includes checkboxes for progress tracking
✅ Balances detail (enough to start) with flexibility (not overly prescriptive)

Next Steps

After creating TASKS.md, you can:

Use build.prompt.md to begin systematic implementation
Review and adjust tasks based on team feedback
Start implementing the first uncompleted task

Related Resources

Required File:

PLANNING.md - Must exist in your project root

Templates (For reference only):

Planning Template: samples/templates/PLANNING.template.md
Tasks Template: samples/templates/TASKS.template.md

Implementation Prompts:

build.prompt.md - Use this to implement tasks once TASKS.md is created

Note: This prompt does not create PLANNING.md. Use create-plan.prompt.md or create it manually before using this prompt.

# Create Project Tasks - Tactical Execution Prompt ## Purpose This prompt guides GitHub Copilot through creating a comprehensive TASKS.md document that breaks down a project plan into actionable implementation tasks. --- ## Instructions to Copilot You are tasked with creating a tactical implementation plan based on an existing strategic project plan. The project has a PLANNING.md file that defines the vision, architecture, and roadmap. **Before starting, verify that PLANNING.md exists in the project. If it doesn't exist, inform the user that this file is required and cannot proceed with creating tasks.** ### Your Goal Create a comprehensive TASKS.md file in the project root that provides: - Actionable, specific implementation tasks - Logical task organization and sequencing - Clear acceptance criteria for each task - Progress tracking with checkboxes --- ## Project Context **Additional Context (Optional):** {{context}} --- ## TASKS.md Structure Create a TASKS.md file with the following sections: ### 1. Initial Setup & Research Environment configuration and foundational tasks: - [ ] Development environment setup - [ ] Install required tools and dependencies - [ ] Configure version control and branching strategy - [ ] Research and prototype key technologies - [ ] Set up development database/services ### 2. Architecture & Design Design artifacts before coding begins: - [ ] Create system architecture diagrams - [ ] Define data models and schemas - [ ] Design API contracts and interfaces - [ ] Create component interaction diagrams - [ ] Document security architecture ### 3. Core Components Development Implementation tasks for each component identified in PLANNING.md: - [ ] Component 1: Basic structure - [ ] Component 1: Core functionality - [ ] Component 1: Unit tests - [ ] Component 1: Error handling - [ ] [Repeat for each component] ### 4. Integration & Configuration Connect components and configure the system: - [ ] Integrate Component A with Component B - [ ] Configure environment variables - [ ] Set up configuration management - [ ] Implement logging and monitoring - [ ] Configure external service connections ### 5. Azure Service Integration (if applicable) Set up and integrate cloud resources: - [ ] Provision Azure resources - [ ] Configure authentication and authorization - [ ] Set up managed identities - [ ] Implement Azure service connections - [ ] Configure monitoring and alerts ### 6. Testing & Quality Assurance Comprehensive testing strategy: - [ ] Write integration tests - [ ] Write end-to-end tests - [ ] Perform load/performance testing - [ ] Security testing and vulnerability scans - [ ] Verify all requirements met ### 7. Documentation Create user and developer documentation: - [ ] Write README with setup instructions - [ ] Document API endpoints and usage - [ ] Create architecture documentation - [ ] Write user guides - [ ] Document troubleshooting procedures ### 8. Deployment & Release Prepare for production deployment: - [ ] Set up CI/CD pipeline - [ ] Configure production environment - [ ] Create deployment runbook - [ ] Perform dry-run deployment - [ ] Deploy to production - [ ] Post-deployment verification ### 9. Phase 2+ Features (Future Work) Advanced features from later phases: - [ ] [Feature from Phase 2] - [ ] [Feature from Phase 3] - [ ] [Additional enhancements] ### 10. Discovered During Work Dynamic section for emergent tasks: - [ ] [Tasks discovered during implementation] --- ## How to Use This Prompt ### Creating Tasks from Existing Plan: ``` I have PLANNING.md ready. Please create TASKS.md. Expected actions: 1. Verify that PLANNING.md exists 2. Read and analyze the PLANNING.md file 3. Extract components, phases, and requirements 4. Create TASKS.md with all sections and specific tasks 5. Organize tasks in logical implementation order 6. Review the task list with me ``` ### Creating Tasks with Specific Focus: ``` Create TASKS.md based on PLANNING.md, focusing on [specific area or phase]. Expected actions: 1. Verify PLANNING.md exists 2. Read the planning document 3. Create comprehensive TASKS.md 4. Give extra detail to the specified focus area 5. Ensure dependencies are clear ``` --- ## Task Writing Guidelines ### Each Task Should: - ✅ Be specific and actionable (verb + noun + context) - ✅ Have clear acceptance criteria - ✅ Be small enough to complete in one session (2-8 hours) - ✅ Have obvious dependencies identified - ✅ Include testing requirements where applicable ### Task Format Examples: **Good Tasks:** - [ ] Implement user authentication using Azure AD B2C with JWT validation - [ ] Create REST API endpoint for feedback submission with JSON schema validation - [ ] Write unit tests for sentiment analysis service achieving >80% coverage **Poor Tasks:** - [ ] Build the backend (too vague) - [ ] Make it work (no specific outcome) - [ ] Fix bugs (not specific enough) ### Task Organization: - ✅ Group related tasks together - ✅ Order tasks by dependency (prerequisites first) - ✅ Separate MVP tasks from enhancement tasks - ✅ Use sub-sections for major components - ✅ Include checkboxes for progress tracking --- ## Example Output **User:** "I have PLANNING.md for a customer feedback analysis system. Create TASKS.md." **Expected Copilot Response:** "I'll create a comprehensive task list based on your PLANNING.md. Let me first verify the file exists and review the plan..." [Reads PLANNING.md] "I've reviewed your planning document. I can see: - 3 main components: Feedback API, Analysis Service, Dashboard - Azure AI Language for sentiment analysis - Cosmos DB for storage - 3-phase roadmap Creating TASKS.md now with tasks organized by setup, design, component development, integration, testing, and deployment..." [Creates detailed TASKS.md] "I've created TASKS.md with 47 specific tasks organized into logical sections: - Initial Setup: 6 tasks for environment and tools - Architecture & Design: 5 tasks for diagrams and data models - Core Components: 18 tasks across 3 components - Integration: 8 tasks for connecting services - Azure Integration: 5 tasks for cloud setup - Testing: 6 tasks for comprehensive QA - Documentation: 4 tasks - Deployment: 5 tasks for CI/CD and production Phase 2+ features are captured but not detailed yet. Ready to begin implementation using build.prompt.md, or would you like to review and adjust any tasks first?" **If PLANNING.md doesn't exist:** "I cannot create TASKS.md because PLANNING.md is missing. PLANNING.md is required to understand: - What components need to be built - The technical architecture and approach - The phased roadmap and priorities Please create PLANNING.md first using `create-plan.prompt.md` or manually using the template in `samples/templates/`. Once PLANNING.md exists, I can generate a comprehensive task list." --- ## Best Practices ### Task Creation - ✅ Base tasks directly on components in PLANNING.md - ✅ Break large tasks into smaller sub-tasks - ✅ Include testing tasks for each component - ✅ Don't forget documentation and deployment tasks - ✅ Capture Phase 2+ features but don't detail them yet ### Organization - ✅ Group by logical workflow (setup → design → build → test → deploy) - ✅ Within each group, order by dependency - ✅ Use clear section headers - ✅ Number tasks if helpful for reference ### Clarity - ✅ Use action verbs (implement, create, configure, test, deploy) - ✅ Be specific about what "done" looks like - ✅ Include relevant technology names - ✅ Reference specific files or components when known ### Azure Projects (when applicable) - ✅ Include Azure resource provisioning tasks - ✅ Add tasks for authentication setup - ✅ Include monitoring and logging configuration - ✅ Consider cost optimization tasks - ✅ Plan for CI/CD with Azure DevOps or GitHub Actions --- ## Troubleshooting **If PLANNING.md doesn't exist:** - Stop and inform the user - Direct them to create PLANNING.md first - Do not attempt to create PLANNING.md yourself **If PLANNING.md is too vague:** - Ask user to clarify specific sections - Suggest updating PLANNING.md before creating tasks - Make reasonable assumptions but document them **If task list becomes too large:** - Focus on Phase 1/MVP tasks in detail - Summarize Phase 2+ tasks at high level - Suggest breaking into multiple epics or sprints **If dependencies are complex:** - Create a dependency section at the top - Use task numbering for cross-referencing - Consider creating a task dependency diagram --- ## Success Criteria A good TASKS.md document: - ✅ Translates all PLANNING.md components into concrete tasks - ✅ Provides clear, actionable items that can be started immediately - ✅ Includes all aspects: setup, development, testing, documentation, deployment - ✅ Has tasks small enough to complete in one session - ✅ Shows clear progression and dependencies - ✅ Includes checkboxes for progress tracking - ✅ Balances detail (enough to start) with flexibility (not overly prescriptive) --- ## Next Steps After creating TASKS.md, you can: 1. Use `build.prompt.md` to begin systematic implementation 2. Review and adjust tasks based on team feedback 3. Start implementing the first uncompleted task --- ## Related Resources **Required File:** - `PLANNING.md` - Must exist in your project root **Templates (For reference only):** - Planning Template: `samples/templates/PLANNING.template.md` - Tasks Template: `samples/templates/TASKS.template.md` **Implementation Prompts:** - `build.prompt.md` - Use this to implement tasks once TASKS.md is created **Note:** This prompt does not create PLANNING.md. Use `create-plan.prompt.md` or create it manually before using this prompt.

{ "prompt": "# Create Project Tasks - Tactical Execution Prompt\n\n## Purpose\nThis prompt guides GitHub Copilot through creating a comprehensive TASKS.md document that breaks down a project plan into actionable implementation tasks.\n\n---\n\n## Instructions to Copilot\n\nYou are tasked with creating a tactical implementation plan based on an existing strategic project plan. The project has a PLANNING.md file that defines the vision, architecture, and roadmap.\n\n**Before starting, verify that PLANNING.md exists in the project. If it doesn't exist, inform the user that this file is required and cannot proceed with creating tasks.**\n\n### Your Goal\n\nCreate a comprehensive TASKS.md file in the project root that provides:\n- Actionable, specific implementation tasks\n- Logical task organization and sequencing\n- Clear acceptance criteria for each task\n- Progress tracking with checkboxes\n\n---\n\n## Project Context\n\n**Additional Context (Optional):** {{context}}\n\n---\n\n## TASKS.md Structure\n\nCreate a TASKS.md file with the following sections:\n\n### 1. Initial Setup & Research\nEnvironment configuration and foundational tasks:\n- [ ] Development environment setup\n- [ ] Install required tools and dependencies\n- [ ] Configure version control and branching strategy\n- [ ] Research and prototype key technologies\n- [ ] Set up development database/services\n\n### 2. Architecture & Design\nDesign artifacts before coding begins:\n- [ ] Create system architecture diagrams\n- [ ] Define data models and schemas\n- [ ] Design API contracts and interfaces\n- [ ] Create component interaction diagrams\n- [ ] Document security architecture\n\n### 3. Core Components Development\nImplementation tasks for each component identified in PLANNING.md:\n- [ ] Component 1: Basic structure\n- [ ] Component 1: Core functionality\n- [ ] Component 1: Unit tests\n- [ ] Component 1: Error handling\n- [ ] [Repeat for each component]\n\n### 4. Integration & Configuration\nConnect components and configure the system:\n- [ ] Integrate Component A with Component B\n- [ ] Configure environment variables\n- [ ] Set up configuration management\n- [ ] Implement logging and monitoring\n- [ ] Configure external service connections\n\n### 5. Azure Service Integration (if applicable)\nSet up and integrate cloud resources:\n- [ ] Provision Azure resources\n- [ ] Configure authentication and authorization\n- [ ] Set up managed identities\n- [ ] Implement Azure service connections\n- [ ] Configure monitoring and alerts\n\n### 6. Testing & Quality Assurance\nComprehensive testing strategy:\n- [ ] Write integration tests\n- [ ] Write end-to-end tests\n- [ ] Perform load/performance testing\n- [ ] Security testing and vulnerability scans\n- [ ] Verify all requirements met\n\n### 7. Documentation\nCreate user and developer documentation:\n- [ ] Write README with setup instructions\n- [ ] Document API endpoints and usage\n- [ ] Create architecture documentation\n- [ ] Write user guides\n- [ ] Document troubleshooting procedures\n\n### 8. Deployment & Release\nPrepare for production deployment:\n- [ ] Set up CI/CD pipeline\n- [ ] Configure production environment\n- [ ] Create deployment runbook\n- [ ] Perform dry-run deployment\n- [ ] Deploy to production\n- [ ] Post-deployment verification\n\n### 9. Phase 2+ Features (Future Work)\nAdvanced features from later phases:\n- [ ] [Feature from Phase 2]\n- [ ] [Feature from Phase 3]\n- [ ] [Additional enhancements]\n\n### 10. Discovered During Work\nDynamic section for emergent tasks:\n- [ ] [Tasks discovered during implementation]\n\n---\n\n## How to Use This Prompt\n\n### Creating Tasks from Existing Plan:\n\n```\nI have PLANNING.md ready. Please create TASKS.md.\n\nExpected actions:\n1. Verify that PLANNING.md exists\n2. Read and analyze the PLANNING.md file\n3. Extract components, phases, and requirements\n4. Create TASKS.md with all sections and specific tasks\n5. Organize tasks in logical implementation order\n6. Review the task list with me\n```\n\n### Creating Tasks with Specific Focus:\n\n```\nCreate TASKS.md based on PLANNING.md, focusing on [specific area or phase].\n\nExpected actions:\n1. Verify PLANNING.md exists\n2. Read the planning document\n3. Create comprehensive TASKS.md\n4. Give extra detail to the specified focus area\n5. Ensure dependencies are clear\n```\n\n---\n\n## Task Writing Guidelines\n\n### Each Task Should:\n- ✅ Be specific and actionable (verb + noun + context)\n- ✅ Have clear acceptance criteria\n- ✅ Be small enough to complete in one session (2-8 hours)\n- ✅ Have obvious dependencies identified\n- ✅ Include testing requirements where applicable\n\n### Task Format Examples:\n\n**Good Tasks:**\n- [ ] Implement user authentication using Azure AD B2C with JWT validation\n- [ ] Create REST API endpoint for feedback submission with JSON schema validation\n- [ ] Write unit tests for sentiment analysis service achieving >80% coverage\n\n**Poor Tasks:**\n- [ ] Build the backend (too vague)\n- [ ] Make it work (no specific outcome)\n- [ ] Fix bugs (not specific enough)\n\n### Task Organization:\n- ✅ Group related tasks together\n- ✅ Order tasks by dependency (prerequisites first)\n- ✅ Separate MVP tasks from enhancement tasks\n- ✅ Use sub-sections for major components\n- ✅ Include checkboxes for progress tracking\n\n---\n\n## Example Output\n\n**User:** \"I have PLANNING.md for a customer feedback analysis system. Create TASKS.md.\"\n\n**Expected Copilot Response:**\n\n\"I'll create a comprehensive task list based on your PLANNING.md. Let me first verify the file exists and review the plan...\"\n\n[Reads PLANNING.md]\n\n\"I've reviewed your planning document. I can see:\n- 3 main components: Feedback API, Analysis Service, Dashboard\n- Azure AI Language for sentiment analysis\n- Cosmos DB for storage\n- 3-phase roadmap\n\nCreating TASKS.md now with tasks organized by setup, design, component development, integration, testing, and deployment...\"\n\n[Creates detailed TASKS.md]\n\n\"I've created TASKS.md with 47 specific tasks organized into logical sections:\n- Initial Setup: 6 tasks for environment and tools\n- Architecture & Design: 5 tasks for diagrams and data models\n- Core Components: 18 tasks across 3 components\n- Integration: 8 tasks for connecting services\n- Azure Integration: 5 tasks for cloud setup\n- Testing: 6 tasks for comprehensive QA\n- Documentation: 4 tasks\n- Deployment: 5 tasks for CI/CD and production\n\nPhase 2+ features are captured but not detailed yet. Ready to begin implementation using build.prompt.md, or would you like to review and adjust any tasks first?\"\n\n**If PLANNING.md doesn't exist:**\n\n\"I cannot create TASKS.md because PLANNING.md is missing. PLANNING.md is required to understand:\n- What components need to be built\n- The technical architecture and approach\n- The phased roadmap and priorities\n\nPlease create PLANNING.md first using `create-plan.prompt.md` or manually using the template in `samples/templates/`. Once PLANNING.md exists, I can generate a comprehensive task list.\"\n\n---\n\n## Best Practices\n\n### Task Creation\n- ✅ Base tasks directly on components in PLANNING.md\n- ✅ Break large tasks into smaller sub-tasks\n- ✅ Include testing tasks for each component\n- ✅ Don't forget documentation and deployment tasks\n- ✅ Capture Phase 2+ features but don't detail them yet\n\n### Organization\n- ✅ Group by logical workflow (setup → design → build → test → deploy)\n- ✅ Within each group, order by dependency\n- ✅ Use clear section headers\n- ✅ Number tasks if helpful for reference\n\n### Clarity\n- ✅ Use action verbs (implement, create, configure, test, deploy)\n- ✅ Be specific about what \"done\" looks like\n- ✅ Include relevant technology names\n- ✅ Reference specific files or components when known\n\n### Azure Projects (when applicable)\n- ✅ Include Azure resource provisioning tasks\n- ✅ Add tasks for authentication setup\n- ✅ Include monitoring and logging configuration\n- ✅ Consider cost optimization tasks\n- ✅ Plan for CI/CD with Azure DevOps or GitHub Actions\n\n---\n\n## Troubleshooting\n\n**If PLANNING.md doesn't exist:**\n- Stop and inform the user\n- Direct them to create PLANNING.md first\n- Do not attempt to create PLANNING.md yourself\n\n**If PLANNING.md is too vague:**\n- Ask user to clarify specific sections\n- Suggest updating PLANNING.md before creating tasks\n- Make reasonable assumptions but document them\n\n**If task list becomes too large:**\n- Focus on Phase 1/MVP tasks in detail\n- Summarize Phase 2+ tasks at high level\n- Suggest breaking into multiple epics or sprints\n\n**If dependencies are complex:**\n- Create a dependency section at the top\n- Use task numbering for cross-referencing\n- Consider creating a task dependency diagram\n\n---\n\n## Success Criteria\n\nA good TASKS.md document:\n- ✅ Translates all PLANNING.md components into concrete tasks\n- ✅ Provides clear, actionable items that can be started immediately\n- ✅ Includes all aspects: setup, development, testing, documentation, deployment\n- ✅ Has tasks small enough to complete in one session\n- ✅ Shows clear progression and dependencies\n- ✅ Includes checkboxes for progress tracking\n- ✅ Balances detail (enough to start) with flexibility (not overly prescriptive)\n\n---\n\n## Next Steps\n\nAfter creating TASKS.md, you can:\n1. Use `build.prompt.md` to begin systematic implementation\n2. Review and adjust tasks based on team feedback\n3. Start implementing the first uncompleted task\n\n---\n\n## Related Resources\n\n**Required File:**\n- `PLANNING.md` - Must exist in your project root\n\n**Templates (For reference only):**\n- Planning Template: `samples/templates/PLANNING.template.md`\n- Tasks Template: `samples/templates/TASKS.template.md`\n\n**Implementation Prompts:**\n- `build.prompt.md` - Use this to implement tasks once TASKS.md is created\n\n**Note:** This prompt does not create PLANNING.md. Use `create-plan.prompt.md` or create it manually before using this prompt.", "variables": [ "context" ], "notes": "You are tasked with creating a tactical implementation plan based on an existing strategic project plan. The project has a PLANNING.md file that defines the vision, architecture, and roadmap.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/HillPhelmuth/AgenticRpg", "path": ".github/prompts/create-tasks.prompt.md", "ref": "18eb01183c4d61534644de13ff4e6dd95348ca51", "url": "https://github.com/HillPhelmuth/AgenticRpg/blob/18eb01183c4d61534644de13ff4e6dd95348ca51/.github/prompts/create-tasks.prompt.md", "key": "HillPhelmuth/AgenticRpg/.github/prompts/create-tasks.prompt.md" } }, "model_hints": [ "Claude Sonnet 4.5 (copilot)" ] }

create-tasks

About