evergreen

Create/Update Evergreen docs

A good project has easy to reach local docs. Locate them! If this project does not: explain the user the benfits of these.

Docs MD - Evergreen Project Docs

• typically in docs/ as EvergreenPascalCaseFile.md
• capture decisons, pitfalls, designs, architecture, etc.
• used for in-depth learning
• used for investigations
• not used every small coding task
• can relate to project issues/ MD files and other Evergreen docs

Issues MD - Specific Current/Past Issues

• capture concrete and specific issues, incl.
  • design issues
  • behavior issues
  • bugs
  • features
• have a status to show what was done and what is open
• can ref. Evergreen docs and other issues

Task

1. Recap the current session regarding:

• project work
• work effectiveness and efficienty
• agentic coding insights
• overall learnings
• architecture changes
• etc.

2. Document all findings and learnings:

• primarily in the Evergreen docs/ MD
• but also update issues/ MD as needed
• close issues as needed
• create new issues as needed to keep Evergreens clean
• overhaul Evergreens if they are too stale
• archive/delete Evergreens when their value diminishes
• update issues index files (isuses/README.md or issues/index.md)
• update Evergreens index files (docs/README.md or docs/index.md)

3. Apply your agentic automation and documentaion skills.

• tell the user what you would do differently
• tell the user where you failed to discover docs or project status
• propose improvements for the agent harness (AGENTS.md, etc.); but do not do them yet. Let the user decide
• skip step 3 if all is OK and there are no major issues