|
| 1 | +# 📈 Daily Progress |
| 2 | + |
| 3 | +> For an overview of all available workflows, see the [main README](../README.md). |
| 4 | +
|
| 5 | +The [daily progress workflow](../workflows/daily-progress.md?plain=1) is an automated workflow that runs daily (Monday through Friday at 2am UTC) to work systematically on your repository's feature roadmap. This workflow acts as an autonomous developer that researches project goals, creates development plans, and implements features through a structured multi-step process. |
| 6 | + |
| 7 | +## Installation |
| 8 | + |
| 9 | +```bash |
| 10 | +gh aw add daily-progress -r githubnext/agentics --pr |
| 11 | +``` |
| 12 | + |
| 13 | +This creates a pull request to add the workflow to your repository. After merging the PR and syncing to main, you can start a run of this workflow immediately by running: |
| 14 | + |
| 15 | +```bash |
| 16 | +gh aw run daily-progress |
| 17 | +``` |
| 18 | + |
| 19 | +**Mandatory Checklist** |
| 20 | + |
| 21 | +* [ ] I have read the notes on coding tasks in the [main README](../README.md) and understand the implications. |
| 22 | + |
| 23 | +* [ ] I understand that this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access. |
| 24 | + |
| 25 | +* [ ] I am a repository admin or have sufficient permissions, and am happy for this workflow to create issues, pull requests, and push new branches to the repository. |
| 26 | + |
| 27 | +* [ ] I have enabled "Allow GitHub Actions to create and approve pull requests" in the repository settings under "Actions > General" |
| 28 | + |
| 29 | +* [ ] I have considered enabling "Always suggest updating pull request branches" in the repository settings |
| 30 | + |
| 31 | +* [ ] If in a fork, I have enabled "GitHub Actions" and "GitHub Issues" in the fork repository settings |
| 32 | + |
| 33 | +* [ ] I will review all pull requests and issues created by this workflow very carefully, and carefully monitor the repository. |
| 34 | + |
| 35 | +## Configuration |
| 36 | + |
| 37 | +This workflow requires no configuration and works out of the box. However, you can customize it as follows: |
| 38 | + |
| 39 | +1. **Local configuration**: Customize development focus areas, coding standards, and workflow behavior. Local configuration can be done in `.github/workflows/agentics/daily-progress.config.md`. |
| 40 | + |
| 41 | +2. **Build steps**: The workflow will automatically create a build configuration file at `.github/actions/daily-progress/build-steps/action.yml` to set up the development environment for feature work. |
| 42 | + |
| 43 | +After editing run `gh aw compile` to update the workflow and commit all changes to the default branch. |
| 44 | + |
| 45 | +## How it Works |
| 46 | + |
| 47 | +The Daily Progress workflow follows a systematic 7-step process: |
| 48 | + |
| 49 | +### 1. Roadmap Research |
| 50 | +- Searches for an existing roadmap issue titled "Daily Roadmap Progress: Research, Roadmap and Plan" |
| 51 | +- If no roadmap exists, conducts comprehensive research into the project's goals, features, and target audience |
| 52 | +- Analyzes existing documentation, issues, pull requests, and project files |
| 53 | +- Creates a detailed roadmap issue with development priorities |
| 54 | + |
| 55 | +### 2. Build Configuration Setup |
| 56 | +- Checks for `.github/actions/daily-progress/build-steps/action.yml` |
| 57 | +- If missing, researches typical build/setup steps for the project |
| 58 | +- Creates the build configuration file and submits a pull request |
| 59 | +- Ensures the repository is properly configured for automated development work |
| 60 | + |
| 61 | +### 3. Goal Selection |
| 62 | +- Reads the project roadmap and any maintainer feedback |
| 63 | +- Reviews existing pull requests to avoid conflicts |
| 64 | +- Selects an appropriate goal from the roadmap to work on |
| 65 | +- Updates the roadmap if it needs refreshing |
| 66 | + |
| 67 | +### 4. Feature Development |
| 68 | +- Creates a new branch for the selected goal |
| 69 | +- Implements code changes to work toward the goal |
| 70 | +- Ensures existing tests pass and adds new tests when appropriate |
| 71 | +- Applies code formatting and linting standards |
| 72 | + |
| 73 | +### 5. Pull Request Creation |
| 74 | +- Creates a draft pull request with the implemented changes |
| 75 | +- Provides detailed description of what was done and why |
| 76 | +- Ensures no unwanted files are included in the PR |
| 77 | +- Links back to the roadmap issue |
| 78 | + |
| 79 | +### 6. Issue Reporting |
| 80 | +- If development fails, creates an issue summarizing the problems encountered |
| 81 | +- Provides context for future development attempts |
| 82 | + |
| 83 | +### 7. Communication |
| 84 | +- Updates the roadmap issue with progress information |
| 85 | +- Links to created pull requests or issues |
| 86 | +- Seeks clarification if unexpected failures occur |
| 87 | + |
| 88 | +## What it reads from GitHub |
| 89 | + |
| 90 | +- Repository contents and file structure |
| 91 | +- Existing issues and pull requests |
| 92 | +- Project documentation and configuration files |
| 93 | +- Actions workflow runs and CI/CD configurations |
| 94 | +- Development container configurations |
| 95 | +- Project boards and roadmaps |
| 96 | + |
| 97 | +## What it creates |
| 98 | + |
| 99 | +- **Planning Issues**: Creates roadmap and research issues for project direction |
| 100 | +- **Configuration Pull Requests**: Adds build and setup configurations |
| 101 | +- **Feature Pull Requests**: Implements new features and improvements as draft PRs |
| 102 | +- **Progress Issues**: Reports on development challenges or failures |
| 103 | +- **Issue Comments**: Updates roadmap issues with progress information |
| 104 | +- Requires `issues: write` and `pull-requests: write` permissions |
| 105 | + |
| 106 | +## What web searches it performs |
| 107 | + |
| 108 | +- Researches project roadmap information and feature development best practices |
| 109 | +- Looks up documentation for technologies used in the project |
| 110 | +- Searches for implementation patterns and code examples |
| 111 | +- May research industry trends relevant to the project goals |
| 112 | + |
| 113 | +## What bash commands it runs |
| 114 | + |
| 115 | +- Repository analysis and exploration commands |
| 116 | +- Build and test commands to ensure code quality |
| 117 | +- Code formatting and linting tools |
| 118 | +- Git operations for branch management and commits |
| 119 | +- Package management commands (npm, pip, etc.) |
| 120 | +- Any commands needed for feature development and validation |
| 121 | + |
| 122 | +## Use Cases |
| 123 | + |
| 124 | +- **Continuous Feature Development**: Automatically work on project roadmap items daily |
| 125 | +- **Technical Debt Reduction**: Systematically improve code quality and documentation |
| 126 | +- **Research and Planning**: Maintain up-to-date project roadmaps and development plans |
| 127 | +- **Automated Maintenance**: Regular updates, dependency management, and improvements |
| 128 | +- **Proof of Concept Development**: Explore new features and implementation approaches |
| 129 | + |
| 130 | +## Monitoring and Control |
| 131 | + |
| 132 | +- **Draft Pull Requests**: All feature changes are created as draft PRs for human review |
| 133 | +- **Roadmap Issues**: Central tracking of project goals and progress |
| 134 | +- **Scheduled Execution**: Runs only on weekdays to respect team schedules |
| 135 | +- **Timeout Protection**: Limited to 30 minutes per run with 48-hour stop-after |
| 136 | +- **Safe Outputs**: Controlled limits on issues and PRs created |
| 137 | + |
| 138 | +## Human in the loop |
| 139 | + |
| 140 | +- Review and approve all draft pull requests created by the workflow |
| 141 | +- Provide feedback on roadmap issues to guide development priorities |
| 142 | +- Monitor progress and adjust goals based on changing project needs |
| 143 | +- Validate that automated changes align with project standards and goals |
| 144 | +- Merge approved pull requests and close completed roadmap items |
0 commit comments