/where - Location Discovery
Find WHERE components are located and WHERE new files should be placed.
System Prompt
EXECUTION DIRECTIVE: When /where is invoked, you MUST:
- IMMEDIATELY search the filesystem and database
- Return exact paths - not approximate, verify they exist
- Explain organization - why files are where they are
- Suggest placement - for new files, based on conventions
Separation of Concerns
| Command | Responsibility | /where's Role |
|---|---|---|
/what | WHAT exists | /where: WHERE it lives |
/which | WHO for task | /where: WHERE to find them |
/how | HOW to do | /where: WHERE to look for guides |
/where | LOCATION | Primary: paths and placement |
Usage
# Find component location
/where is orchestrator # Find agent file
/where is /classify # Find command file
/where is MoE classifier # Find script/module
# Find proper placement
/where put new-agent.md # Where should agent go?
/where put deploy-script.sh # Where should script go?
/where put security-guide.md # Where should doc go?
# Find by type
/where are agents # All agent locations
/where are workflows # All workflow locations
/where are standards # All standard locations
Response Format
For /where is <component>
┌─────────────────────────────────────────────────────────────┐
│ WHERE IS: orchestrator │
├─────────────────────────────────────────────────────────────┤
│ TYPE: agent │
│ │
│ PRIMARY LOCATION │
│ ──────────────── │
│ Relative: agents/orchestrator.md │
│ Absolute: /Users/halcasteel/PROJECTS/coditect-rollout- │
│ master/submodules/core/coditect-core/agents/ │
│ orchestrator.md │
│ │
│ RELATED FILES │
│ ───────────── │
│ • Skill: skills/orchestration/SKILL.md │
│ • Test: tests/agents/test_orchestrator.py │
│ • Docs: docs/guides/ORCHESTRATION-GUIDE.md │
│ │
│ WHY HERE │
│ ──────── │
│ All agents live in agents/*.md per CODITECT convention. │
│ See: coditect-core-standards/CODITECT-STANDARD-AGENTS.md │
├─────────────────────────────────────────────────────────────┤
│ QUICK ACCESS │
│ ──────────── │
│ cat agents/orchestrator.md │
│ /what can orchestrator │
└─────────────────────────────────────────────────────────────┘
For /where put <file>
┌─────────────────────────────────────────────────────────────┐
│ WHERE PUT: new-security-agent.md │
├─────────────────────────────────────────────────────────────┤
│ RECOMMENDED LOCATION │
│ ──────────────────── │
│ Path: agents/new-security-agent.md │
│ │
│ WHY │
│ ─── │
│ • File extension .md + "agent" in name → agent component │
│ • All agents live in agents/ directory │
│ • Naming: lowercase-with-hyphens.md │
│ │
│ CONVENTION │
│ ────────── │
│ Standard: CODITECT-STANDARD-AGENTS.md │
│ Pattern: agents/<name>.md │
│ │
│ AFTER PLACEMENT │
│ ─────────────── │
│ 1. Verify frontmatter (YAML required) │
│ 2. Register: python3 scripts/component-indexer.py │
│ 3. Classify: /classify agents/new-security-agent.md │
│ │
│ OR USE AUTOMATED │
│ ──────────────── │
│ ./scripts/component-create.sh agent new-security-agent \ │
│ "Description here" │
│ (Handles placement, registration, classification) │
└─────────────────────────────────────────────────────────────┘
For /where are <type>
┌─────────────────────────────────────────────────────────────┐
│ WHERE ARE: agents │
├─────────────────────────────────────────────────────────────┤
│ LOCATION: agents/ │
│ COUNT: 150 files │
│ PATTERN: agents/*.md │
│ │
│ STRUCTURE │
│ ───────── │
│ agents/ │
│ ├── orchestrator.md │
│ ├── senior-architect.md │
│ ├── code-reviewer.md │
│ ├── devops-engineer.md │
│ ├── security-specialist.md │
│ ├── ... (145 more) │
│ └── README.md (index) │
│ │
│ NAMING CONVENTION │
│ ───────────────── │
│ • lowercase-with-hyphens │
│ • descriptive-name.md │
│ • No spaces, underscores, or capitals │
│ │
│ STANDARD │
│ ──────── │
│ coditect-core-standards/CODITECT-STANDARD-AGENTS.md │
└─────────────────────────────────────────────────────────────┘
Directory Map
| Type | Location | Pattern |
|---|---|---|
| Agents | agents/ | *.md |
| Commands | commands/ | *.md |
| Skills | skills/*/ | SKILL.md |
| Scripts | scripts/ | *.py, *.sh |
| Hooks | hooks/ | *.md, *.py, *.sh |
| Workflows | workflows/ | *.yaml, *.json |
| Standards | coditect-core-standards/ | CODITECT-STANDARD-*.md |
| ADRs | internal/architecture/adrs/ | ADR-*.md |
| Guides | docs/guides/ | *-GUIDE.md |
Gap Detection
When location unclear:
┌─────────────────────────────────────────────────────────────┐
│ GAP DETECTED: /where put unclear-file.xyz │
├─────────────────────────────────────────────────────────────┤
│ Cannot determine proper location for this file type. │
│ │
│ SUGGESTIONS │
│ ─────────── │
│ 1. Check file purpose: │
│ • Agent definition? → agents/ │
│ • Command? → commands/ │
│ • Script? → scripts/ │
│ • Documentation? → docs/ │
│ │
│ 2. Check naming conventions: │
│ /how best naming-conventions │
│ │
│ 3. If new file type, consider: │
│ • Add to directory standards │
│ • Document in DIRECTORY-STRUCTURE-STANDARD.md │
│ │
│ This gap has been logged for system evolution. │
└─────────────────────────────────────────────────────────────┘
Related Commands
| Command | Purpose |
|---|---|
/what is <component> | Details including location |
/how put <file> | How to properly place |
/component-create | Auto-places new components |
Success Output
When location discovery completes:
✅ COMMAND COMPLETE: /where
Query: <is|put|are>
Target: <component-or-type>
Location: <path>
Verified: YES
Completion Checklist
Before marking complete:
- Location verified to exist
- Exact path provided
- Placement rationale explained
- Related files identified
Failure Indicators
This command has FAILED if:
- ❌ Path not verified to exist
- ❌ No exact location provided
- ❌ Gap not logged for unknown
- ❌ Approximate paths given
When NOT to Use
Do NOT use when:
- Need component details (use
/what) - Need task-to-agent matching (use
/which) - Need rationale (use
/why)
Anti-Patterns (Avoid)
| Anti-Pattern | Problem | Solution |
|---|---|---|
| Guess locations | Wrong placement | Verify path exists |
| Skip conventions | Inconsistent structure | Follow standards |
| Ignore related files | Miss dependencies | List related files |
Principles
This command embodies:
- #4 Separation of Concerns - Explains directory organization rationale
- #6 Clear, Understandable, Explainable - Exact paths, not approximations
Full Standard: CODITECT-STANDARD-AUTOMATION.md
Version: 1.0.0 | Created: 2026-01-03 | Author: CODITECT Team