.cursor/skills/status-query-handling/SKILL.md
--- name: status-query-handling description: Guides status query handling protocol: find all related documents (plan, progress, status, complete), synthesize comprehensive answer. Use when user asks about status, progress, or completion. --- # Status Query Handling ## Trigger Phrases When user says: - "where are we with [topic]" - "what's the status of [topic]" - "how far along is [topic]" - "what's complete in [topic]" - "show me progress on [topic]" - "update me on [topic]" ## Mandatory Pr
npx skillsauth add avra-cadavra/avrai .cursor/skills/status-query-handlingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When user says:
⚠️ CRITICAL: Read ALL related documents, not just one.
Find ALL related documents:
# Search for all document types
glob_file_search('**/*[topic]*.md')
glob_file_search('**/*[topic]*plan*.md')
glob_file_search('**/*[topic]*complete*.md')
glob_file_search('**/*[topic]*progress*.md')
glob_file_search('**/*[topic]*status*.md')
glob_file_search('**/*[topic]*summary*.md')
glob_file_search('**/*[topic]*COMPLETE*.md')
glob_file_search('**/*[topic]*PROGRESS*.md')
Plan Documents
*_plan.md*PLAN.md*plan*.mdCompletion Documents
*complete*.md*COMPLETE*.md*_complete.mdProgress Documents
*progress*.md*PROGRESS*.md*_progress.mdStatus Documents
*status*.md*STATUS*.md*_status.md*update*.mdSummary Documents
*summary*.md*SUMMARY*.md*_summary.mdUser asks: "Where are we with [topic]?"
↓
Step 1: Search ALL document types (5 min)
├─ Search by filename patterns
├─ Search by content (grep)
└─ Find plan, complete, progress, status, summary
↓
Step 2: Read ALL found documents (15-20 min)
├─ Read plan document
├─ Read completion document
├─ Read progress document
├─ Read status document
└─ Read summary document (if exists)
↓
Step 3: Synthesize comprehensive answer (10 min)
├─ What's planned
├─ What's complete
├─ What's in progress
├─ What's blocked
└─ What's next
## Status: [Topic]
### What's Planned
[From plan document]
### What's Complete
[From completion document]
### What's In Progress
[From progress/status documents]
### Blockers
[From blockers/status documents]
### What's Next
[From plan/status documents]
docs/plans/methodology/START_HERE_NEW_TASK.md - Status query protocol.cursorrules - Status Query Triggers sectiondevelopment
--- name: world-model-development description: Guides world model development patterns: state/action encoders, ONNX inference, feature extraction pipeline, latency budgets. Use when implementing world model components, state encoders, action encoders, feature extractors, or ONNX models. Core skill for Phases 3-6. --- # World Model Development Patterns ## Core Principle All world model components follow LeCun's autonomous machine intelligence framework. State observations flow through a percep
tools
Implements base workflow controller patterns for multi-step processes. Use when creating complex workflows that require orchestration of multiple steps with error handling and rollback.
testing
--- name: widget-test-patterns description: Guides widget test patterns: BLoC testing, user interactions, state changes, material app setup. Use when writing widget tests, testing UI components, or validating widget behavior. --- # Widget Test Patterns ## Core Pattern Widget tests verify UI behavior: user interactions, state changes, and visual display. ## Basic Widget Test Setup ```dart testWidgets('widget displays correctly', (WidgetTester tester) async { // Arrange: Create widget awa
testing
--- name: test-template-generation description: Generates test templates: unit, widget, integration, service tests following project patterns. Use when creating new tests or ensuring tests follow project standards. --- # Test Template Generation ## Available Templates Test templates are located in `test/templates/`: - `unit_test_template.dart` - `widget_test_template.dart` - `integration_test_template.dart` - `service_test_template.dart` ## Unit Test Template ```dart /// SPOTS Component Uni