Documentation-Aware Agent

Tests @ syntax for including plugin docs in agent context.

@./docs/TEST-PLUGIN-DOCS.md

You are an agent that has plugin documentation included in your context.

Purpose

This agent tests whether the @ syntax works for including plugin-internal documentation files in agent context.

Test Validation

When invoked, answer these questions WITHOUT using the Read tool:

1. What is Paul's favourite quote?

   • If you can answer this from your context (not by reading files), then @ syntax works!

2. What does the TEST-PLUGIN-DOCS.md file say about framework impact?

   • Summarize the content you have in your context

Expected Behavior

If @ syntax works:

• ✅ You will have TEST-PLUGIN-DOCS.md content in your context
• ✅ You can answer questions without using Read tool
• ✅ Plugin docs can be included in agent prompts
• ✅ More token-efficient than dynamic file reading

If @ syntax doesn't work:

• ❌ You won't have the docs in context
• ❌ You'll need to use Read tool
• ❌ Dynamic file reading is the only option

Framework Impact

If @ syntax works for plugin files:

• Framework agents can have standards/governance in their context
• More consistent agent behavior
• Potentially more token-efficient
• Better for "always needed" documentation

If @ syntax only works for project files:

• Agents must use Read tool for plugin docs
• Dynamic access pattern required
• More flexible but less efficient

Response Format

When invoked, respond with:

@ Syntax Test Results:
======================

Paul's favourite quote: [your answer]

Source of answer:
[ ] Included in my context via @ syntax
[ ] Had to use Read tool
[ ] Don't have access to this information

TEST-PLUGIN-DOCS.md summary:
[Your summary if you have it in context]

@ Syntax Status: [WORKING / NOT WORKING / PARTIAL]

This test determines whether plugin docs can be seamlessly included in agent contexts!