Spaces:
Runtime error
Runtime error
Aryan Mishra
feat: initial commit - Multilingual ABSA project setup with 6 phases, 36 requirements
a6b96c2 | # Planner — Load Graph Context | |
| > Loaded by `gsd-planner` at the `load_graph_context` step. | |
| Check for knowledge graph: | |
| ```bash | |
| ls .planning/graphs/graph.json 2>/dev/null | |
| ``` | |
| If graph.json exists, check freshness: | |
| ```bash | |
| _GSD_SHIM_NAME="gsd-tools.cjs"; _GSD_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; GSD_TOOLS="${_GSD_RUNTIME_ROOT}/gsd-core/bin/${_GSD_SHIM_NAME}"; if [ -f "$GSD_TOOLS" ]; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif [ -f "${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; elif command -v gsd-tools >/dev/null 2>&1; then GSD_TOOLS="$(command -v gsd-tools)"; gsd_run() { "$GSD_TOOLS" "$@"; }; elif [ -f "/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and gsd-tools is not on PATH. Run: npx -y @opengsd/gsd-core@latest --claude --local" >&2; exit 1; fi | |
| gsd_run graphify status | |
| ``` | |
| If the status response has `stale: true`, note for later: "Graph is {age_hours}h old -- treat semantic relationships as approximate." Include this annotation inline with any graph context injected below. | |
| Query the graph for phase-relevant dependency context (single query per D-06): | |
| ```bash | |
| gsd_run graphify query "<phase-goal-keyword>" --budget 2000 | |
| ``` | |
| Use the keyword that best captures the phase goal. Examples: | |
| - Phase "User Authentication" -> query term "auth" | |
| - Phase "Payment Integration" -> query term "payment" | |
| - Phase "Database Migration" -> query term "migration" | |
| If the query returns nodes and edges, incorporate as dependency context for planning: | |
| - Which modules/files are semantically related to this phase's domain | |
| - Which subsystems may be affected by changes in this phase | |
| - Cross-document relationships that inform task ordering and wave structure | |
| If no results or graph.json absent, continue without graph context. | |