This directory contains a working bash script that implements the 9-stage Developer Lifecycle, enhanced implementation techniques including the Five-Try Rule and systematic retry strategies, and a comprehensive workflow example showing how to apply these techniques in practice.
developer-lifecycle/
├── README.md # This file
├── lifecycle-workflow.sh # ✅ Complete 9-stage workflow automation script
└── examples/ # Empty directory for future examples
A full implementation would include:
developer-lifecycle/
├── README.md # This file
├── lifecycle-workflow.sh # ✅ Complete 9-stage workflow automation script
├── comprehensive-workflow-example.md # ✅ Complete 7-step implementation example
├── enhanced-implementation-techniques.md # ✅ Five-Try Rule, systematic retry, integration strategies
├── stage-prompts/ # Detailed prompts for each stage
│ ├── 01-problem-definition.md
│ ├── 02-technical-planning.md
│ ├── 03-requirements-analysis.md
│ ├── 04-issue-generation.md
│ ├── 05-specification-creation.md
│ ├── 06-implementation.md
│ ├── 07-testing.md
│ ├── 08-deployment.md
│ └── 09-monitoring.md
├── examples/ # Example implementations
│ ├── jwt-authentication/ # Complete JWT auth example
│ └── api-endpoints/ # REST API example
└── ci-integration/ # CI/CD pipeline integration
├── github-actions.yml
├── gitlab-ci.yml
└── azure-pipelines.yml
- Problem Definition → Clear problem statement and success criteria
- Technical Planning → Architecture decisions and technical approach
- Requirements Analysis → Detailed functional and non-functional requirements
- Issue Generation → Kanban-ready work items with acceptance criteria
- Specification Creation → Executable specifications and API contracts
- Implementation → AI-assisted coding following specifications
- Testing → Comprehensive test suite execution and validation
- Deployment → Automated deployment with rollback capabilities
- Monitoring → Production monitoring and alerting setup
- Bash shell (macOS, Linux, or WSL on Windows)
- Basic command line knowledge
- AI assistant access (Claude, ChatGPT, etc.) for implementing generated templates
-
Make the script executable:
chmod +x lifecycle-workflow.sh
-
Run complete lifecycle for a feature:
./lifecycle-workflow.sh --feature "JWT Authentication" -
Run specific stage:
./lifecycle-workflow.sh --stage 6 --context "implement-jwt-auth" -
View help:
./lifecycle-workflow.sh --help
The lifecycle-workflow.sh script creates a lifecycle-output/ directory with:
- Stage 1:
01-problem-statement.md- Problem definition template - Stage 2:
02-technical-plan.md- Architecture and technology decisions - Stage 3:
03-requirements.md- Functional and non-functional requirements - Stage 4:
04-kanban-issues.json- Ready-to-import GitHub/JIRA issues - Stage 5:
05-api-specification.yaml- OpenAPI specification template - Stage 6:
implementation/README.md- Implementation guide and setup instructions - Stage 7:
testing/test-plan.md- Comprehensive testing strategy - Stage 8:
deployment/deploy.sh- Deployment automation script - Stage 9:
monitoring/alerts.yaml- Monitoring and alerting configuration
# Generate all lifecycle stages for JWT authentication
./lifecycle-workflow.sh --feature "User Authentication System"
# Output: lifecycle-output/ directory with all 9 stages# Generate only the technical planning stage
./lifecycle-workflow.sh --stage 2 --context "microservices architecture"
# Generate implementation guide with specific context
./lifecycle-workflow.sh --stage 6 --context "OAuth2 integration with existing API"# 1. Define the problem and generate all stages
./lifecycle-workflow.sh --feature "Payment Processing"
# 2. Review generated templates in lifecycle-output/
ls -la lifecycle-output/
# 3. Use AI assistant to flesh out the templates
# 4. Import Kanban issues to your project management tool
# 5. Follow the implementation guide- Review Generated Templates: Examine all files in
lifecycle-output/directory - Enhance with AI: Use the templates as starting points for AI conversations
- Import Issues: Load
04-kanban-issues.jsoninto GitHub Issues or JIRA - Implement API: Use
05-api-specification.yamlto generate API stubs - Follow Implementation Guide: Use
implementation/README.mdfor development setup - Execute Tests: Implement tests following
testing/test-plan.md - Deploy: Use
deployment/deploy.shas deployment automation baseline - Monitor: Configure alerts using
monitoring/alerts.yaml
- Complete automation of all 9 lifecycle stages
- Template generation for immediate use with AI assistants
- Structured output organized by stage and file type
- Command-line interface with help and validation
- Colored output for clear stage progression
- Error handling and validation
The generated templates work well with:
- GitHub Issues: Import
04-kanban-issues.jsonusing GitHub CLI or API - JIRA: Convert JSON issues to JIRA format for import
- Azure DevOps: Transform issues into work items
- OpenAPI: Use
05-api-specification.yamlwith Swagger/Postman - Testing: Implement test plans using generated
testing/test-plan.md - CI/CD: Adapt
deployment/deploy.shfor your pipeline
- Use generated templates as context for Claude, ChatGPT, or Copilot
- Feed stage outputs into AI for detailed implementation
- Leverage structured prompts for consistent results
To extend this example:
- Add more detailed stage prompts in a
stage-prompts/directory - Create complete example implementations in
examples/ - Add CI/CD integration templates in
ci-integration/ - Enhance the bash script with additional features
The current script provides a solid foundation for the complete Developer Lifecycle pattern.