Working with VF Agent Resources

Even though the old prompt folder is gone, the same idea lives in files under vf-agent/. Here is the quick workflow:

1. Pick the right agent. Open vf-agent/agents/<role>.md (e.g., dev.md, pm.md, architect.md) to understand that persona’s responsibilities and activation instructions. The orchestrator file (orchestrator.md) describes how these agents are composed into a guided workflow.
2. Use the matching task/template. Each agent helps execute a defined task (e.g., writing a doc, creating a story) and provides links to the applicable template in vf-agent/templates/. Duplicate or adapt the template for your own doc to keep tone and structure consistent.
3. Consult the knowledge base. Before authoring anything, read the relevant file in vf-agent/data/knowledge_base/starter-docs/ (e.g., chatbot-reference.md, payments-reference.md, tech-stack.md). These files mirror today’s docs and provide the exact language the agents were trained on.
4. Follow the checklists. The vf-agent/checklists/ directory contains practical walkthroughs for handoffs, QA, releases, and other routines. Use them to validate that you didn’t skip a step.

Pro tip: vf-agent/core-config.yaml lists the knowledge files every planning agent loads. If you need to add new reference material, update that config so the agents are aware of it as soon as you commit.

This structure replaces the old prompt paste workflow. Instead of copying prompt text into a chat window, open the matching agent/task/checklist and follow the steps there to keep your work aligned with the VF Agent methodology.