Spec Context Localization (FEATURE_DIR)

Overview

requirements/*.md

{FEATURE_DIR}

When to Use

• You are about to read/write:

  {FEATURE_DIR}/requirements/raw.md | clarify.md | competitors.md | solutions.md | prd.md

• You are unsure which spec pack you are currently in (worried about reading/writing to the wrong directory)
• You encounter context errors such as "non-compliant branch name/incomplete directory structure/missing .aisdlc"

The Only Correct Approach (PowerShell)

. ".\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

Hard Rules (Must Follow)

• Locate first, then read/write: Before any read/write operation on

  requirements/*.md

  , you must run the above script and echo

  FEATURE_DIR=...

  .
• Stop on failure: When

  Get-SpecContext

  reports an error, you must stop immediately and must not continue generating/writing file content (otherwise, you will almost certainly deviate from the correct context).
• Only use FEATURE_DIR to construct paths: All subsequent paths must use

  $FEATURE_DIR

  as the prefix (guessing relative paths using the current working directory is prohibited).

Common Mistakes

• Executing on a non-spec branch: If the branch name does not conform to the

  {num}-{short-name}

  format, the spec pack cannot be located.
• Manually writing paths like

  .aisdlc/specs/...

  : Humans make mistakes, and AI is even more prone to errors; you must rely on the script's output.
• Continuing to "generate documents": As long as the context validation fails, stop and first fix the branch/directory structure.