Prompt file imported from dheerink-visionplanner/opgelucht-generator (.github/prompts/implement-plan.prompt.md). Copyright stays with the author.

Implement by following an implementation plan

Name: implement-plan
Author: dheerink-visionplanner

Implement a user story based on the implementation plan provided as comment to the issue. For example, when passed ID 42, read the issue with ID 42 on GitHub and find the implementation plan in the comments.

Important: This agent follows a systematic 6-step implementation process to ensure comprehensive feature delivery. The implementation plan contains all necessary context for autonomous implementation.

Implementation Plan input

The implementation plan can be found in the comments of the issue. Important: If you can't find it in the comments, abort the process.

Read and follow all instructions in the implementation plan completely.

Execution Process

1. Load the Implementation Plan

Read the specified implementation plan thoroughly
Understand the context, constraints, and all requirements
Follow all instructions in the implementation plan exactly
Ensure you have all needed context to implement the requirements fully
Perform additional web and codebase search as necessary to fill any gaps

2. Plan the Implementation

Think before you execute the plan. Create a comprehensive plan addressing all requirements
Break down complex tasks into smaller, manageable steps using TODO tracking
Use task management tools to create and track your implementation plan
Identify implementation patterns from existing code to follow
Reference the architectural patterns and conventions specified in the requirements

3. Execute the Plan

Implement the requirements from the implementation plan systematically
Write all necessary code following the patterns and conventions identified
Follow the ordered implementation path provided in the implementation plan
Ensure integration with existing codebase as specified
Implement comprehensive error handling as documented

4. Validate

Run each validation gate specified in the requirements document
Execute all test commands (e.g., npm test, dotnet test)
Run linting and code quality checks
Perform any performance benchmarks if applicable
Fix any failures that occur
Re-run until all validation gates pass

5. Complete

Ensure all checklist items from the requirements are done
Run final validation suite to confirm everything works
Report completion status with summary of implemented features
Read the requirements document again to ensure you've implemented everything
Verify all main flow and alternate scenarios are covered

6. Reference the Requirements Document

You can always reference the requirements document again for clarification
If any requirement is unclear, implement based on the best practices and patterns identified
Use the code examples and file references provided in the requirements

Implementation Guidelines

UI/UX

The UI should follow the design found on the mockups referenced in the implementation plan
Mirror component structure, props, and state management from similar existing components
Ensure responsive design and accessibility standards are met

Code Quality

Follow existing architectural patterns and conventions
Mirror the coding style and patterns from referenced files
Implement comprehensive error handling as specified
Ensure proper integration with existing systems

Testing and Validation

Execute all validation gates in the specified order
Address any test failures immediately
Ensure all code quality checks pass
Verify performance meets any specified benchmarks

Documentation

Update relevant documentation if specified in requirements
Follow documentation patterns established in the codebase
Include any necessary inline code comments

Success Criteria

Implementation is complete when:

All requirements from the document are implemented
All validation gates pass
Code follows established patterns and conventions
Integration with existing systems works correctly
All error handling scenarios are covered
Performance meets specified criteria

The implementation should be ready for production use without additional modifications.

# Implement by following an implementation plan Implement a user story based on the implementation plan provided as comment to the issue. For example, when passed ID `42`, read the issue with ID `42` on GitHub and find the implementation plan in the comments. **Important**: This agent follows a systematic 6-step implementation process to ensure comprehensive feature delivery. The implementation plan contains all necessary context for autonomous implementation. ## Implementation Plan input The implementation plan can be found in the comments of the issue. Important: If you can't find it in the comments, abort the process. Read and follow all instructions in the implementation plan completely. ## Execution Process ### 1. Load the Implementation Plan - Read the specified implementation plan thoroughly - Understand the context, constraints, and all requirements - Follow all instructions in the implementation plan exactly - Ensure you have all needed context to implement the requirements fully - Perform additional web and codebase search as necessary to fill any gaps ### 2. Plan the Implementation - Think before you execute the plan. Create a comprehensive plan addressing all requirements - Break down complex tasks into smaller, manageable steps using TODO tracking - Use task management tools to create and track your implementation plan - Identify implementation patterns from existing code to follow - Reference the architectural patterns and conventions specified in the requirements ### 3. Execute the Plan - Implement the requirements from the implementation plan systematically - Write all necessary code following the patterns and conventions identified - Follow the ordered implementation path provided in the implementation plan - Ensure integration with existing codebase as specified - Implement comprehensive error handling as documented ### 4. Validate - Run each validation gate specified in the requirements document - Execute all test commands (e.g., `npm test`, `dotnet test`) - Run linting and code quality checks - Perform any performance benchmarks if applicable - Fix any failures that occur - Re-run until all validation gates pass ### 5. Complete - Ensure all checklist items from the requirements are done - Run final validation suite to confirm everything works - Report completion status with summary of implemented features - Read the requirements document again to ensure you've implemented everything - Verify all main flow and alternate scenarios are covered ### 6. Reference the Requirements Document - You can always reference the requirements document again for clarification - If any requirement is unclear, implement based on the best practices and patterns identified - Use the code examples and file references provided in the requirements ## Implementation Guidelines ### UI/UX - The UI should follow the design found on the mockups referenced in the implementation plan - Mirror component structure, props, and state management from similar existing components - Ensure responsive design and accessibility standards are met ### Code Quality - Follow existing architectural patterns and conventions - Mirror the coding style and patterns from referenced files - Implement comprehensive error handling as specified - Ensure proper integration with existing systems ### Testing and Validation - Execute all validation gates in the specified order - Address any test failures immediately - Ensure all code quality checks pass - Verify performance meets any specified benchmarks ### Documentation - Update relevant documentation if specified in requirements - Follow documentation patterns established in the codebase - Include any necessary inline code comments ## Success Criteria Implementation is complete when: - All requirements from the document are implemented - All validation gates pass - Code follows established patterns and conventions - Integration with existing systems works correctly - All error handling scenarios are covered - Performance meets specified criteria The implementation should be ready for production use without additional modifications.

{ "prompt": "# Implement by following an implementation plan\n\nImplement a user story based on the implementation plan provided as comment to the issue. For example, when passed ID `42`, read the issue with ID `42` on GitHub and find the implementation plan in the comments.\n\n**Important**: This agent follows a systematic 6-step implementation process to ensure\ncomprehensive feature delivery. The implementation plan contains all necessary context\nfor autonomous implementation.\n\n## Implementation Plan input\n\nThe implementation plan can be found in the comments of the issue. Important: If you can't find it in the comments, abort the process. \n\nRead and follow all instructions in the implementation plan completely.\n\n## Execution Process\n\n### 1. Load the Implementation Plan\n\n- Read the specified implementation plan thoroughly\n- Understand the context, constraints, and all requirements\n- Follow all instructions in the implementation plan exactly\n- Ensure you have all needed context to implement the requirements fully\n- Perform additional web and codebase search as necessary to fill any gaps\n\n### 2. Plan the Implementation\n\n- Think before you execute the plan. Create a comprehensive plan addressing all requirements\n- Break down complex tasks into smaller, manageable steps using TODO tracking\n- Use task management tools to create and track your implementation plan\n- Identify implementation patterns from existing code to follow\n- Reference the architectural patterns and conventions specified in the requirements\n\n### 3. Execute the Plan\n\n- Implement the requirements from the implementation plan systematically\n- Write all necessary code following the patterns and conventions identified\n- Follow the ordered implementation path provided in the implementation plan\n- Ensure integration with existing codebase as specified\n- Implement comprehensive error handling as documented\n\n### 4. Validate\n\n- Run each validation gate specified in the requirements document\n- Execute all test commands (e.g., `npm test`, `dotnet test`)\n- Run linting and code quality checks\n- Perform any performance benchmarks if applicable\n- Fix any failures that occur\n- Re-run until all validation gates pass\n\n### 5. Complete\n\n- Ensure all checklist items from the requirements are done\n- Run final validation suite to confirm everything works\n- Report completion status with summary of implemented features\n- Read the requirements document again to ensure you've implemented everything\n- Verify all main flow and alternate scenarios are covered\n\n### 6. Reference the Requirements Document\n\n- You can always reference the requirements document again for clarification\n- If any requirement is unclear, implement based on the best practices and patterns identified\n- Use the code examples and file references provided in the requirements\n\n## Implementation Guidelines\n\n### UI/UX\n\n- The UI should follow the design found on the mockups referenced in the implementation plan\n- Mirror component structure, props, and state management from similar existing components\n- Ensure responsive design and accessibility standards are met\n\n### Code Quality\n- Follow existing architectural patterns and conventions\n- Mirror the coding style and patterns from referenced files\n- Implement comprehensive error handling as specified\n- Ensure proper integration with existing systems\n\n### Testing and Validation\n- Execute all validation gates in the specified order\n- Address any test failures immediately\n- Ensure all code quality checks pass\n- Verify performance meets any specified benchmarks\n\n### Documentation\n- Update relevant documentation if specified in requirements\n- Follow documentation patterns established in the codebase\n- Include any necessary inline code comments\n\n## Success Criteria\n\nImplementation is complete when:\n- All requirements from the document are implemented\n- All validation gates pass\n- Code follows established patterns and conventions\n- Integration with existing systems works correctly\n- All error handling scenarios are covered\n- Performance meets specified criteria\n\nThe implementation should be ready for production use without additional modifications.", "variables": [], "notes": "Implement a user story based on an implementation plan Mode: agent. Tools: changes, codebase, editFiles, extensions, fetch, findTestFiles, githubRepo, new, openSimpleBrowser, problems, runCommands, runNotebooks.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/dheerink-visionplanner/opgelucht-generator", "path": ".github/prompts/implement-plan.prompt.md", "ref": "e0999fe25b7c6b667467e57b4a6837d70acb29c3", "url": "https://github.com/dheerink-visionplanner/opgelucht-generator/blob/e0999fe25b7c6b667467e57b4a6837d70acb29c3/.github/prompts/implement-plan.prompt.md", "key": "dheerink-visionplanner/opgelucht-generator/.github/prompts/implement-plan.prompt.md" } } }

implement-plan

About