If a user mentions a "plan" or asks about the plan, and they have used the conductor extension in the current session, they are likely referring to the conductor/tracks.md file or one of the track plans (conductor/tracks/<track_id>/plan.md).
PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track):
-
Identify Index: Determine the relevant index file:
- Project Context:
conductor/index.md - Track Context:
a. Resolve and read the Tracks Registry (via Project Context).
b. Find the entry for the specific
<track_id>. c. Follow the link provided in the registry to locate the track's folder. The index file is<track_folder>/index.md. d. Fallback: If the track is not yet registered (e.g., during creation) or the link is broken: 1. Resolve the Tracks Directory (via Project Context). 2. The index file is<Tracks Directory>/<track_id>/index.md.
- Project Context:
-
Check Index: Read the index file and look for a link with a matching or semantically similar label.
-
Resolve Path: If a link is found, resolve its path relative to the directory containing the
index.mdfile.- Example: If
conductor/index.mdlinks to./workflow.md, the full path isconductor/workflow.md.
- Example: If
-
Fallback: If the index file is missing or the link is absent, use the Default Path keys below.
-
Verify: You MUST verify the resolved file actually exists on the disk.
Standard Default Paths (Project):
- Product Definition:
conductor/product.md - Tech Stack:
conductor/tech-stack.md - Workflow:
conductor/workflow.md - Product Guidelines:
conductor/product-guidelines.md - Tracks Registry:
conductor/tracks.md - Tracks Directory:
conductor/tracks/
Standard Default Paths (Track):
- Specification:
conductor/tracks/<track_id>/spec.md - Implementation Plan:
conductor/tracks/<track_id>/plan.md - Metadata:
conductor/tracks/<track_id>/metadata.json