62 lines
2.5 KiB
Markdown
62 lines
2.5 KiB
Markdown
# Setup Development Environment for Story
|
|
|
|
## Purpose
|
|
Ensure development environment is ready and validated for story implementation. Focused on story-specific setup and validation.
|
|
|
|
## Inputs
|
|
- `story_file`: Path to the approved story file
|
|
|
|
## Task Execution
|
|
|
|
### 1. Environment Health Check
|
|
- Verify project-specific development services are running (check project documentation for required services)
|
|
- Check service connectivity and responsiveness based on project architecture
|
|
- Validate port availability and configuration as defined in project setup
|
|
- Ensure no service conflicts or failures in the development stack
|
|
|
|
### 2. Development Dependencies
|
|
- Verify all required dependencies are installed
|
|
- Check package versions match project requirements
|
|
- Validate development tools are available
|
|
- Ensure environment variables are properly configured
|
|
|
|
### 3. Build and Quality Validation
|
|
- Execute complete build process to ensure success
|
|
- Run linting and type checking to establish baseline
|
|
- Verify all existing tests pass before new development
|
|
- Check that development server starts successfully
|
|
|
|
### 4. Authentication and Security
|
|
- Test authentication flow with development credentials (if project requires authentication)
|
|
- Verify authorization rules are working according to project security model
|
|
- Check security configurations are properly set per project requirements
|
|
- Validate API access and permissions as defined in project documentation
|
|
|
|
### 5. Story-Specific Validation
|
|
- Review story requirements for any special environment needs
|
|
- Check if story requires specific tools or configurations
|
|
- Validate access to necessary external services (if applicable)
|
|
- Ensure development environment supports story implementation
|
|
|
|
## Success Criteria
|
|
- All services responding correctly
|
|
- Build process completes without errors
|
|
- Baseline quality checks pass (lint, typecheck, tests)
|
|
- Authentication working with test credentials
|
|
- Development environment ready for story work
|
|
|
|
## Outputs
|
|
- `environment_status`: "READY" or "ISSUES_FOUND"
|
|
- `issues_found`: List of any problems requiring resolution
|
|
- `setup_notes`: Any special configurations or notes for development
|
|
|
|
## Failure Actions
|
|
- Document specific environment issues
|
|
- Attempt automatic resolution of common problems
|
|
- Provide clear remediation steps
|
|
- Halt development until environment is stable
|
|
|
|
## Notes
|
|
- Lightweight validation focused on story development readiness
|
|
- Not comprehensive infrastructure validation (use validate-infrastructure for that)
|
|
- Designed to quickly verify environment is ready for immediate story work |