haiku
When writing a haiku for this bot, follow these conventions:
Refresh Product status from current work and source evidence.
$ npx -y skills add agno-agi/agno --skill refresh --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/refreshContext preview
The summary Claude sees to decide when to auto-load this skill.
Refresh Product status from current work and source evidence.
name: refresh description: Refresh Product status from current work and source evidence.
Read the Product identified in the message. Read its playbook, then call refresh_company_product for that Product. This applies its archive window (metadata.archive_window_days, default 14) and returns Project completion proposals saved in the wiki. It never completes a Project. Present those proposals for a human to accept through the Project transition API; never transition directly. Read the remaining Projects and Tasks, then inspect configured Sources with read_company_source. Reflect observed progress and failures in status.md using its current version. On a conflict, read again and incorporate intervening changes. Propose changes for human review; never accept work or mark a Task Ready or Done. Remove references to archived work from status.md so it no longer enters executor context. Keep brief.md and status.md; maintenance only deletes recognized generated pages older than the window. If nothing changed, return a quiet successful check without writing duplicate pages. Report a maintenance failure instead of claiming success.
For each Source, call read_company_source without path for a paged, content-free index. Use pattern and next_offset to narrow discovery. Pass a returned path to read one document; next_content_offset continues large documents. Compare the full-document content_hash across fragments and reread if it changes. Never infer content from an index entry. Use intake_company_source for Task proposals; propose_company_task is unavailable to Routines.