Files
msd-core/sdk/src/query/mvp.ts
Tom Boucher 2d32ad82be fix(plan-phase): remove agent: directive that caused OpenCode subagent dispatch (#3156) (#3206)
* feat(roadmap): parse **Mode:** field on phase sections

Adds a 'mode' field to roadmap.get-phase and roadmap.analyze outputs.
Recognizes '**Mode:** mvp' lines in phase sections; lowercased + trimmed.
Forward-compat: unrecognized values preserved verbatim, no enum check.

Foundation for --mvp flag in plan-phase (PRD: vertical-mvp-slice).

* feat(plan-phase): parse --mvp flag and resolve MVP_MODE

Resolution order: CLI flag → ROADMAP **Mode:** field → workflow.mvp_mode
config → false. Walking Skeleton gate fires for new-project Phase 1.
Wires MVP_MODE + WALKING_SKELETON into gsd-planner subagent prompt.

Per PRD vertical-mvp-slice Phase 1 (Q1, Q2, Q4).

* docs(planner): add vertical-slice planning reference

New reference loaded by gsd-planner when MVP_MODE=true. Defines slice
ordering, Walking Skeleton rules, and anti-patterns. Referenced from
plan-phase workflow MVP_MODE wiring.

* docs(planner): add SKELETON.md template

Template emitted by gsd-planner under WALKING_SKELETON=true. Captures
architectural decisions and out-of-scope list for new-project Phase 1.

* chore(inventory): register new planner references

Added planner-mvp-mode.md and skeleton-template.md to INVENTORY.md and
INVENTORY-MANIFEST.json. References now: 53.

* feat(gsd-planner): add MVP Mode Detection section

Mode-switched branch in the existing planner agent (per Q4: single agent).
Vertical-slice decomposition rules, Walking Skeleton handling, and
TDD-mode compatibility. Heavy guidance lives in references/planner-mvp-mode.md.

* test(plan-phase): add --mvp resolution-chain integration cases

Validates roadmap.get-phase --pick mode and confirms workflow.mvp_mode
default is unset in fresh projects.

* docs(changelog): announce --mvp vertical-slice planning (#2826)

* feat(mvp-phase): add /gsd mvp-phase slash command

Standalone command for vertical MVP planning. Frontmatter only;
heavyweight workflow at get-shit-done/workflows/mvp-phase.md follows
in next commit. Mirrors discuss-phase/edit-phase command shape.

* docs(planner): add user-story-template reference

Defines the canonical 'As a / I want to / So that' format and the
ROADMAP.md / PLAN.md emit rules. Used by mvp-phase workflow and
gsd-planner agent under MVP_MODE.

* docs(planner): add SPIDR splitting reference

Defines size signals, the five SPIDR axes (Spike/Paths/Interfaces/Data/Rules),
the interactive workflow, and anti-patterns. Per PRD Q3 decision: full
interactive flow, not lightweight check. Used by mvp-phase workflow.

* fix(mvp-phase): trim description to fit 100-char budget

* feat(mvp-phase): add mvp-phase workflow

Standalone workflow: phase validation -> user story prompts (As a / I want to /
So that) -> SPIDR splitting check -> ROADMAP write (Mode + Goal) -> delegation
to plan-phase. Per PRD Phase 2 (Q3 full SPIDR; Phase-2-A/B/C/D decisions).

Plan-phase auto-detects MVP via Phase 1's resolution chain, so no flags
are needed when delegating.

* feat(gsd-planner): emit user-story header in PLAN.md under MVP mode

Extends the MVP Mode Detection section (added in Phase 1) so the planner
sources the user story from ROADMAP **Goal:** and emits the bolded
**As a** / **I want to** / **so that** form as the first content under
the phase header in PLAN.md. References user-story-template.md.

* test(mvp-phase): integration smoke test for ROADMAP mutation

Validates roadmap.get-phase output after a workflow-spec'd ROADMAP write:
mode=mvp and goal=full user story. Catches schema drift between workflow
emit and parser expectation. Includes a long-story case (>120 chars) to
confirm SPIDR-rejected stories still parse correctly.

* chore(inventory): register mvp-phase command + 2 new references

Adds /gsd mvp-phase to commands list, mvp-phase workflow to workflows list,
and user-story-template.md + spidr-splitting.md to references. References
count: 53 -> 55.

* docs(changelog): announce /gsd mvp-phase command (#2826)

* fix(mvp-phase): add TEXT_MODE plain-text fallback for non-Claude runtimes (#2012)

* docs(executor): add MVP+TDD gate reference

Defines the runtime gate semantics for execute-phase when both
MVP_MODE and TDD_MODE are true: pre-task verification of failing-test
commit, end-of-phase review escalation from advisory to blocking,
behavior-adding task definition. Loaded conditionally by
execute-phase workflow and gsd-executor agent.

* feat(execute-phase): MVP+TDD runtime gate + blocking review

Resolves MVP_MODE in Step 1 (CLI flag -> roadmap mode -> config -> false).
Adds per-task gate that halts before behavior-adding tasks run if no
failing-test commit exists for the plan. Escalates end-of-phase TDD
review from advisory to blocking when both MVP_MODE and TDD_MODE active.

Also updates INVENTORY-MANIFEST.json to register execute-mvp-tdd.md
(added by Task 1) so manifest-sync tests pass.

Per PRD vertical-mvp-slice Phase 3a (decisions Phase-3-A, Phase-3-Split).

* feat(gsd-executor): add MVP+TDD Gate section

Mirrors the planner's MVP Mode Detection pattern from Phase 1.
Instructs halt-and-report when the runtime gate trips, references
execute-mvp-tdd.md for full semantics. No agent changes outside the
new section.

* test(execute-phase): add MVP+TDD resolution-chain integration cases

Validates roadmap.get-phase --pick mode and confirms workflow.mvp_mode
default is unset in fresh projects. Mirrors the Phase 1 plan-phase
resolution-chain integration test.

* chore(inventory): register execute-mvp-tdd reference

Bumps References count 55 -> 56. Registers execute-mvp-tdd.md.
Adds "init" to PROSE_ALLOWLIST in registry integration test so
bare `gsd-sdk query init` prose examples in plan docs don't
trigger the unregistered-handler guard (real commands are all
init.<subcommand>).

* docs(changelog): announce MVP+TDD runtime gate in execute-phase (#2826)

* docs(verifier): add verify-mvp-mode reference

Defines UAT framing under MVP mode: user-flow walk-through first,
technical checks deferred, coverage check as goal-backward narrowing
to the user story's outcome clause. Loaded conditionally by
verify-work workflow and gsd-verifier agent.

* feat(verify-work): MVP-mode UAT framing — user flow first

Resolves MVP_MODE from phase mode field. Under MVP mode, generates UAT
in three ordered sections: user-flow walk-through (derived from user
story), technical checks (deferred), coverage check (goal-backward).
Falls back to standard UAT generation when mode is null/absent.
User-story-format guard refuses to verify a mode:mvp phase with a
non-user-story goal.

Also updates docs/INVENTORY.md (56 references) and
docs/INVENTORY-MANIFEST.json to register verify-mvp-mode.md added
in Task 1.

Per PRD vertical-mvp-slice Phase 3b (decisions Phase-3-B,
Phase-3-Verify-Structure).

* feat(gsd-verifier): add MVP Mode Verification section

Narrows goal-backward verification to the user-story [outcome] clause
when phase mode is mvp. References verify-mvp-mode.md. Preserves
existing goal-backward methodology for non-MVP phases. User-story-format
guard refuses to verify a mode:mvp phase with a non-user-story goal.

* docs(changelog): announce MVP-mode UAT framing in verify-work (#2826)

* feat(new-project): add Vertical MVP vs Horizontal Layers mode prompt

Asks user at project init how to structure the project. Vertical MVP
emits **Mode:** mvp on every initial roadmap phase (per-phase mode
preserved per PRD Q1). Horizontal Layers falls back to standard
template — no behavioral change for existing flows.

Per PRD vertical-mvp-slice Phase 4 (decision Phase-4-Persistence).

* feat(progress): add MVP-mode user-flow display

When phase has **Mode:** mvp, progress renders user-flow status from
PLAN.md task names alongside standard task progress. Tasks that aren't
user-flow-shaped (technical-sounding) are filtered out of the user-flow
sub-block. Falls back to standard display when mode is null/absent.

Per PRD vertical-mvp-slice Phase 4 (decision Phase-4-Progress).

* feat(stats): add MVP phase count summary

Reads roadmap.analyze (which surfaces mode per phase from Phase 1) and
emits 'Phases: N total | M MVP | K standard' summary line. Suppressed
when MVP_COUNT == 0 to avoid clutter on non-MVP projects.

Per PRD vertical-mvp-slice Phase 4.

* feat(graphify): add MVP-mode visual differentiation

MVP-mode phases render with #22c55e fill color AND ' (MVP)' label
suffix — two-channel signaling for color-blind and grayscale renders.
Standard phases unchanged.

Per PRD vertical-mvp-slice Phase 4 (PRD Q5: distinct visual treatment).

* docs(changelog): announce Phase 4 discovery & progress (#2826)

* chore(release): bump dev to 1.50.0-canary.0 for first 1.50.0 canary

Sets the base version that .github/workflows/canary.yml derives the canary
tag from (strips suffix → base 1.50.0 → next available v1.50.0-canary.N).

This kicks off the 1.50.0 release train, opened by the MVP/TDD/UAT vertical
slice landed across PRs #2867, #2874, #2878, #2880, #2883.

* docs: add CANARY stream README + v1.50.0-canary.1 release notes

- docs/CANARY.md — explains the dev→@canary stream policy, install/rollback
  paths, and when (not) to install canary builds
- docs/RELEASE-v1.50.0-canary.1.md — release notes for the first 1.50.0
  canary cut: vertical MVP/TDD/UAT slice (#2867 + #2874 + #2878 + #2880 +
  #2883), opening the 1.50.0 train under PRD #2826
- docs/README.md — index entry + quick link for the canary stream

* fix(ci/canary): publish gate checks dev branch, not main

Four publish-step `if:` conditions in .github/workflows/canary.yml were
checking `github.ref == 'refs/heads/main'`. Those steps (Tag and push,
Publish to npm, Publish SDK to npm, Verify publish) therefore always
skipped on every workflow_dispatch invocation since canary runs from dev,
never main.

The workflow's own header comment is unambiguous: `dev → @canary`. The
gate was a copy-paste from release.yml (which correctly targets main for
the @next/@latest streams) that was never corrected for the canary stream.

This is why the 1.50.0-canary.1 publish hadn't materialized despite three
green workflow runs. With the gate corrected, the next dispatch will
actually publish.

* ci(release-sdk): make release-sdk.yml dispatchable from the dev branch

The workflow lives on main only, so the GitHub Actions "Use workflow
from" dropdown doesn't list dev — meaning dev → @dev publishes can't be
triggered from the dev branch directly. Add the file to dev so an
operator can dispatch it with branch=dev and tag=dev.

Per project release-stream policy: dev branch publishes canary (@dev).
This is the stream that needs the file most, since main never publishes
@dev itself (main does @next / @latest).

File is byte-identical to main's release-sdk.yml — straight propagation,
no behavioral change. Tracking issues #2925, #2929.

* docs(mvp): canary-prep concept cleanup — CONTEXT.md, mvp-concepts index, --prd interaction (#3176)

* chore(mvp): concept cleanup + cross-ref index for v1.50.0-canary.2 prep

- CONTEXT.md gains 7 MVP domain terms (MVP Mode, User Story, Walking
  Skeleton, Vertical Slice, Behavior-Adding Task, MVP+TDD Gate, SPIDR
  Splitting) so the project glossary matches the shipped surface.
- New get-shit-done/references/mvp-concepts.md indexes the six MVP
  reference files and concept-to-file map so agents and contributors
  can find the right canonical doc without grepping.
- plan-phase.md Walking Skeleton block now documents that --mvp and
  --prd compose orthogonally on Phase 1; no precedence needed.
- INVENTORY/INVENTORY-MANIFEST refreshed for the new reference (58 -> 59).

No behavior change. Canary-prep cleanup ahead of v1.50.0-canary.2.

Surfaced for follow-up (not in this PR):
- MVP_MODE resolution shell block duplicated across plan-phase,
  execute-phase, verify-work workflows (needs a shared workflow-include
  mechanism; structural change).
- Behavior-Adding Task predicate is prose-only; no shared utility.
- User Story regex hardcoded in verify-work; would benefit from a
  central definition consumed by the verifier and the mvp-phase command.

* chore(changeset): set PR number for mvp concept cleanup

* feat(mvp): centralize resolution surfaces + fix SDK roadmap mode parity (#3178)

Three new SDK query verbs replace the architectural duplication surfaced by
the v1.50.0-canary.2 review against dev tip 12c4e565:

  phase.mvp-mode <N> [--cli-flag]
    Single canonical precedence resolver (CLI flag -> ROADMAP **Mode:** mvp
    -> workflow.mvp_mode config -> false). Replaces 4-8 lines of bash that
    were duplicated across plan-phase.md, execute-phase.md, verify-work.md,
    and progress.md. Returns {active, source, roadmap_mode, config_mvp_mode,
    cli_flag_present}.

  task.is-behavior-adding <plan-file> | --task-content <xml>
    Behavior-Adding Task predicate (tdd="true" + <behavior> block + non-test
    source files in <files>). Replaces prose-only specification in
    references/execute-mvp-tdd.md; gsd-executor agent now invokes the verb
    instead of re-inlining the three checks. Returns {is_behavior_adding,
    checks, reason}.

  user-story.validate <text> | --story <text>
    Owns the canonical User Story regex /^As a .+, I want to .+, so that .+\.$/
    previously hardcoded in verify-work.md prose. Consumed by gsd-verifier
    (phase-goal guard) and /gsd-mvp-phase (interactive-prompt validation).
    Returns {valid, slots: {role, capability, outcome}, errors[]}.

Bug fix bundled: sdk/src/query/roadmap.ts searchPhaseInContent now extracts
the mode field from **Mode:**, restoring parity with roadmap.cjs:120-123.
Without this, roadmap.get-phase --pick mode returned null on the native
dispatch path even when the phase had **Mode:** mvp set, causing MVP_MODE
to silently fall through to the config/false branch in every consuming
workflow. The original PRs Phase 1 (#2885) shipped the CJS parser but the
SDK port omitted the field; this fix brings them back to parity.

Workflows + agents updated to call the verbs:
  - plan-phase.md, execute-phase.md, verify-work.md, progress.md call
    phase.mvp-mode (one line replaces the duplicated bash chains).
  - execute-phase.md MVP+TDD gate calls task.is-behavior-adding.
  - verify-work.md goal guard calls user-story.validate.
  - mvp-phase.md interactive prompt validates via user-story.validate.
  - gsd-executor agent references task.is-behavior-adding instead of prose.
  - gsd-verifier agent references user-story.validate instead of inlined regex.

Tests: 24 new vitest tests in sdk/src/query/mvp.test.ts cover all three
verbs + the regression. Two existing contract tests (progress, verify)
updated to assert on the new verb shape. All 60 existing MVP contract
tests pass; golden integration suite (38 + 42 tests) passes.

Closes #3177

* fix(canary.2): unblock release gates for v1.50.0-canary.2

Run 25451329660 (Release SDK Bundle on dev, 2026-05-06T17:41) failed at the
test-suite step with 3 deterministic content/structure gate failures, all
attributable to the MVP umbrella integration in #3178 and the docs sweep
in #3180.

Failure 1: /gsd-mvp-phase undocumented in workflows/help.md
  - tests/bug-2954-help-md-slash-command-stubs.test.cjs requires every
    shipped commands/gsd/<X>.md to have a /gsd-<X> mention in help.md
  - PR #3180 updated docs/COMMANDS.md but missed help.md (which the AI
    agents load in-product)
  - Fix: add a /gsd-mvp-phase entry to help.md right before /gsd-plan-phase

Failures 2 + 3: execute-phase.md (1727) and plan-phase.md (1714) over XL budget (1700)
  - PR #3178 added MVP-mode verb calls (phase.mvp-mode, task.is-behavior-adding,
    user-story.validate) to both workflow files, pushing them past 1700 lines
  - Fix: bump XL_BUDGET 1700 -> 1800 with inline comment pointing at the
    structural follow-up (extract MVP bodies to <workflow>/modes/mvp.md per
    the discuss-phase/modes/ precedent)
  - The structural extract is the right long-term fix but is bigger than
    canary unblock scope; will land in a follow-up after canary cycles

Local verification:
  $ node --test tests/bug-2954-help-md-slash-command-stubs.test.cjs                 tests/workflow-size-budget.test.cjs
  tests 111  pass 111  fail 0

After this lands, re-trigger Release SDK Bundle on dev for v1.50.0-canary.2.

* chore(changeset): set PR number for canary.2 unblock

* fix(codex): generate-claude-md writes to AGENTS.md on Codex runtime

When config.runtime === 'codex' or GSD_RUNTIME=codex, override the
output target to AGENTS.md regardless of claude_md_path, so Codex
projects no longer have GSD sections written to CLAUDE.md by mistake.

Fixes both the CJS (gsd-tools) and SDK (profile-output.ts) paths.
Explicit --output flags are still honoured in both paths.

Closes #3163

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix(plan-phase): remove agent: directive that caused OpenCode subagent dispatch

On OpenCode, any command with `agent: <name>` in its frontmatter is
auto-dispatched to a subagent context where the Agent tool is unavailable.
plan-phase.md and mvp-phase.md both carried `agent: gsd-planner`, causing
them to run inside gsd-planner's subagent context with no ability to spawn
researcher/planner/checker subagents — the orchestrator fell back to inline
execution for all three phases.

Fix: remove `agent: gsd-planner` from both command files so they run in the
main agent context. Also replace the stale `Task` tool in allowed-tools with
`Agent` (the correct dispatcher tool name post-#3168 rename).

Adds a structural regression test that parses YAML frontmatter of every
commands/gsd/*.md file and asserts no command carries an `agent:` directive.

Closes #3156

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix(mvp): address CodeRabbit workflow and contract findings

* fix(execute-phase): use registered state.update query command

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-06 21:51:38 -04:00

293 lines
11 KiB
TypeScript

/**
* MVP-mode query handlers — three centralized seams for the MVP umbrella feature (#2826).
*
* Replaces three architectural duplications surfaced by the v1.50.0-canary.2 review:
*
* 1. **`phase.mvp-mode`** — resolves the precedence chain
* `--mvp` CLI flag → ROADMAP `**Mode:** mvp` → `workflow.mvp_mode` config → false.
* Replaces near-identical bash blocks in `plan-phase.md`, `execute-phase.md`,
* `verify-work.md`, `progress.md`. Single canonical resolution; workflows just
* call the verb and read the boolean.
*
* 2. **`task.is-behavior-adding`** — applies the three-check predicate
* (tdd=true frontmatter AND `<behavior>` block AND non-test source files in `<files>`)
* that was previously prose-only in `references/execute-mvp-tdd.md`. The gsd-executor
* agent now invokes the verb instead of inlining the checks.
*
* 3. **`user-story.validate`** — applies the canonical user-story regex
* `/^As a .+, I want to .+, so that .+\.$/` previously hardcoded in `verify-work.md`
* prose. Consumed by the verifier (phase-goal guard) and by `/gsd-mvp-phase`
* (interactive-prompt validation).
*
* Domain terms: see CONTEXT.md → MVP Mode, User Story, Behavior-Adding Task.
* Concept index: get-shit-done/references/mvp-concepts.md.
*/
import { readFile } from 'node:fs/promises';
import { existsSync } from 'node:fs';
import { relative, resolve, sep } from 'node:path';
import { GSDError, ErrorClassification } from '../errors.js';
import { loadConfig } from '../config.js';
import { roadmapGetPhase } from './roadmap.js';
import type { QueryHandler } from './utils.js';
// ─── phase.mvp-mode ─────────────────────────────────────────────────────────
export type MvpModeSource = 'cli_flag' | 'roadmap' | 'config' | 'none';
interface MvpModeResult {
/** True when MVP mode applies to the phase. */
active: boolean;
/** Which signal in the precedence chain decided the result. */
source: MvpModeSource;
/** The literal value seen in ROADMAP.md `**Mode:**` (lowercased), or null when the field is absent. */
roadmap_mode: string | null;
/** The `workflow.mvp_mode` config value seen at resolution time. */
config_mvp_mode: boolean;
/** True when the caller indicated the `--mvp` CLI flag was present. */
cli_flag_present: boolean;
}
/**
* Resolve MVP mode for a phase. Precedence (first hit wins):
* 1. `--cli-flag` arg on this verb (caller asserts the user passed `--mvp`)
* 2. ROADMAP.md `**Mode:** mvp` for the phase
* 3. `workflow.mvp_mode` config (project-wide default)
* 4. false
*
* @example
* gsd-sdk query phase.mvp-mode 1 # roadmap + config check
* gsd-sdk query phase.mvp-mode 1 --cli-flag # caller saw --mvp on CLI
*/
export const phaseMvpMode: QueryHandler<MvpModeResult> = async (args, projectDir, workstream) => {
const phaseNum = args[0];
if (!phaseNum) {
throw new GSDError(
'Usage: phase.mvp-mode <phase-number> [--cli-flag]',
ErrorClassification.Validation,
);
}
const cliFlagPresent = args.includes('--cli-flag');
// Precedence #2: ROADMAP.md
const phaseResult = await roadmapGetPhase([phaseNum], projectDir, workstream);
const phaseData = phaseResult.data as { found?: boolean; mode?: string | null };
const roadmapMode = phaseData.found && typeof phaseData.mode === 'string'
? phaseData.mode.trim().toLowerCase()
: null;
// Precedence #3: config
const config = await loadConfig(projectDir, workstream);
const wf = (config.workflow ?? {}) as unknown as Record<string, unknown>;
const configMvpMode = Boolean(wf.mvp_mode ?? false);
let active = false;
let source: MvpModeSource = 'none';
if (cliFlagPresent) {
active = true;
source = 'cli_flag';
} else if (roadmapMode === 'mvp') {
active = true;
source = 'roadmap';
} else if (configMvpMode) {
active = true;
source = 'config';
}
return {
data: {
active,
source,
roadmap_mode: roadmapMode,
config_mvp_mode: configMvpMode,
cli_flag_present: cliFlagPresent,
},
};
};
// ─── task.is-behavior-adding ────────────────────────────────────────────────
interface BehaviorAddingResult {
/** True when ALL three predicate checks pass. */
is_behavior_adding: boolean;
/** Per-check breakdown — useful for halt-and-report messages. */
checks: {
tdd_true: boolean;
has_behavior_block: boolean;
has_source_files: boolean;
};
/** Human-readable reason when `is_behavior_adding` is false. */
reason: string | null;
}
/**
* Predicate: does this PLAN.md task add user-visible behavior under MVP+TDD?
*
* Three checks, all required:
* (1) `tdd="true"` frontmatter
* (2) `<behavior>` block names a user-visible outcome (block exists and is non-empty)
* (3) `<files>` includes at least one non-test source file
* (excludes `*.md`, `*.json`, `*.test.*`, `*.spec.*`)
*
* Pure doc-only / config-only / test-only tasks return `is_behavior_adding=false`
* and are exempt from the MVP+TDD Gate.
*
* Canonical specification: get-shit-done/references/execute-mvp-tdd.md.
*
* @example
* gsd-sdk query task.is-behavior-adding ./plans/01-PLAN-auth.md
* gsd-sdk query task.is-behavior-adding --task-content "<task>...</task>"
*/
export const taskIsBehaviorAdding: QueryHandler<BehaviorAddingResult> = async (args, projectDir) => {
let content: string | null = null;
if (args[0] === '--task-content') {
content = args[1] ?? null;
} else if (args[0]) {
const requestedPath = args[0];
const projectRoot = resolve(projectDir ?? process.cwd());
const resolvedTaskPath = resolve(projectRoot, requestedPath);
const rel = relative(projectRoot, resolvedTaskPath);
if (rel === '..' || rel.startsWith(`..${sep}`)) {
throw new GSDError(
`Task file is outside project scope: ${requestedPath}`,
ErrorClassification.Validation,
);
}
if (!existsSync(resolvedTaskPath)) {
throw new GSDError(
`Task file not found: ${requestedPath}`,
ErrorClassification.Validation,
);
}
content = await readFile(resolvedTaskPath, 'utf-8');
}
if (!content) {
throw new GSDError(
'Usage: task.is-behavior-adding <plan-file-path> | --task-content "<xml>"',
ErrorClassification.Validation,
);
}
// Check 1: tdd="true" — accept either single or double quotes, case-insensitive.
const tddTrue = /\btdd\s*=\s*["']true["']/i.test(content);
// Check 2: <behavior>...</behavior> block exists and is non-empty after trim.
const behaviorMatch = content.match(/<behavior>([\s\S]*?)<\/behavior>/i);
const hasBehaviorBlock = Boolean(behaviorMatch && behaviorMatch[1].trim().length > 0);
// Check 3: <files>...</files> includes at least one source file
// (anything that is NOT *.md, *.json, *.test.*, *.spec.*).
const filesMatch = content.match(/<files>([\s\S]*?)<\/files>/i);
let hasSourceFiles = false;
if (filesMatch) {
const filesBody = filesMatch[1];
const fileLines = filesBody
.split(/[\n,]/)
.map(l => l.trim().replace(/^[-*]\s*/, ''))
.filter(Boolean);
hasSourceFiles = fileLines.some(f =>
!/\.md$/i.test(f) &&
!/\.json$/i.test(f) &&
!/\.test\.[^.]+$/i.test(f) &&
!/\.spec\.[^.]+$/i.test(f) &&
!/(^|[\\/])tests?[\\/]/i.test(f) &&
!/\.(yml|yaml|toml|ini|cfg|conf|properties)$/i.test(f) &&
!/(^|[\\/])\.env(\..+)?$/i.test(f)
);
}
const isBehaviorAdding = tddTrue && hasBehaviorBlock && hasSourceFiles;
let reason: string | null = null;
if (!isBehaviorAdding) {
const missing: string[] = [];
if (!tddTrue) missing.push('tdd="true" frontmatter absent');
if (!hasBehaviorBlock) missing.push('<behavior> block missing or empty');
if (!hasSourceFiles) missing.push('<files> has no non-test source file');
reason = `Not behavior-adding: ${missing.join('; ')}`;
}
return {
data: {
is_behavior_adding: isBehaviorAdding,
checks: {
tdd_true: tddTrue,
has_behavior_block: hasBehaviorBlock,
has_source_files: hasSourceFiles,
},
reason,
},
};
};
// ─── user-story.validate ────────────────────────────────────────────────────
interface UserStoryValidateResult {
/** True when the input matches the canonical user-story regex. */
valid: boolean;
/** The literal input string echoed back. */
input: string;
/** Per-slot extraction when `valid` is true; null when invalid. */
slots: { role: string; capability: string; outcome: string } | null;
/** Specific guidance when `valid` is false. */
errors: string[];
}
/**
* The canonical User Story regex — exported so unit tests can assert it directly
* and other modules can import it without re-defining.
*
* Pattern: `As a [role], I want to [capability], so that [outcome].`
*/
export const USER_STORY_REGEX = /^As a (?<role>.+?), I want to (?<capability>.+?), so that (?<outcome>.+?)\.$/;
/**
* Validate that a string matches the User Story format used by MVP-mode phases.
* Used by `gsd-verifier` (phase-goal guard) and `/gsd-mvp-phase` (interactive prompting).
*
* @example
* gsd-sdk query user-story.validate "As a user, I want to log in, so that I can see my data."
* gsd-sdk query user-story.validate --story "<text>"
*/
export const userStoryValidate: QueryHandler<UserStoryValidateResult> = async (args, _projectDir) => {
let input: string | null = null;
if (args[0] === '--story') {
input = args[1] ?? null;
} else if (args[0]) {
input = args.join(' ');
}
if (input === null || input === '') {
throw new GSDError(
'Usage: user-story.validate "<story text>" | --story "<text>"',
ErrorClassification.Validation,
);
}
const match = input.match(USER_STORY_REGEX);
const errors: string[] = [];
let slots: UserStoryValidateResult['slots'] = null;
if (match && match.groups) {
slots = {
role: match.groups.role.trim(),
capability: match.groups.capability.trim(),
outcome: match.groups.outcome.trim(),
};
} else {
if (!/^As a /i.test(input)) errors.push('Must begin with "As a ".');
if (!/, I want to /i.test(input)) errors.push('Must contain ", I want to ".');
if (!/, so that /i.test(input)) errors.push('Must contain ", so that ".');
if (!/\.$/.test(input)) errors.push('Must end with a period.');
if (errors.length === 0) errors.push('Does not match canonical User Story shape.');
}
return {
data: {
valid: match !== null,
input,
slots,
errors,
},
};
};