Skip to content

Latest commit

 

History

History
56 lines (35 loc) · 2.15 KB

File metadata and controls

56 lines (35 loc) · 2.15 KB

📋 Daily Plan

For an overview of all available workflows, see the main README.

The daily plan workflow will run daily to update a planning issue for the team. This planning issue can be used by other workflows as a reference for what the team is working on and what the current priorities are. You can edit the workflow to adjust the planning and report.

Installation

# Install the 'gh aw' extension
gh extension install github/gh-aw

# Add the Daily Plan workflow to your repository
gh aw add githubnext/agentics/daily-plan

This walks you through adding the workflow to your repository and running the workflow for the first time.

Mandatory Checklist

  • If in a fork, enable GitHub Actions and Issues in the fork settings

Configuration

This workflow requires no configuration and works out of the box. You can use local configuration to specify planning focus areas, reporting format, and frequency. Local configuration can be done in .github/workflows/agentics/daily-plan.config.md.

After editing run gh aw compile to update the workflow and commit all changes to the default branch.

What it reads from GitHub

  • Repository contents and file structure
  • Pull requests and their metadata

What it creates

  • Creates new planning issues for the team
  • Updates existing planning issues with current information
  • Requires issues: write permission

What web searches it performs

  • Searches for additional planning information and best practices
  • May look up industry trends or project management insights

Human in the loop

  • Review and validate planning issues created or updated by the workflow
  • Adjust priorities and tasks based on team feedback
  • Add missing context or clarifications to planning issues
  • Use planning issues as input for team coordination and sprint planning
  • Disable or uninstall the workflow if planning automation is not helpful

Activity duration

  • By default this workflow will trigger for at most 30 days, after which it will stop triggering.
  • This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.