| .. | ||
| base-de-conhecimento.md | ||
| captain_architecture_mapping.md | ||
| implementation_plan.md | ||
| jasmine_brain_plan.md | ||
| jasmine_tools_plan.md | ||
| jasmine_unification_plan.md | ||
| README.md | ||
| solucao_ambiente_wuzapi.md | ||
| task.md | ||
| vps_deployment_guide.md | ||
| walkthrough.md | ||
| wuzapi_fix_plan.md | ||
| wuzapi_implementation_plan.md | ||
| wuzapi_walkthrough.md | ||
Collaboration Plans
This directory is the run queue for AI agents and maintainers coordinating work across documentation and playbooks. Treat the list below as an ordered backlog: finish the first plan before moving on to the next unless a human directs otherwise.
Agent Execution Protocol
- Read the queue from top to bottom. The numbering reflects execution priority.
- Open the plan file (e.g., './plans/.md') and review the YAML front matter and the '' wrapper so you understand the goal, required inputs, and success criteria.
- Gather context by visiting the linked documentation and agent playbooks referenced in the "Agent Lineup" and "Documentation Touchpoints" tables.
- Execute the stages exactly as written, capturing evidence and updating linked docs as instructed. If a stage cannot be completed, record the reason inside the plan before pausing.
- Close out the plan by updating any TODOs, recording outcomes in the "Evidence & Follow-up" section, and notifying maintainers if human review is required.
- Return here and pick the next plan in the queue. Always leave the README and plan files consistent with the work performed.
Plan Queue (process in order)
How To Create Or Update Plans
- Run "ai-context plan " to scaffold a new plan template.
- Run "ai-context plan --fill" (optionally with "--dry-run") to have an LLM refresh the plan using the latest repository context.
- Cross-link any new documentation or agent resources you introduce so future runs stay discoverable.