story-context-bridge

story-context-bridge

Extracts structured handoff artifacts from a completed domain agent's run and formats them for injection into the next domain agent's context. This ensures cross-domain implementation consistency — when the backend agent runs after the DB agent, it knows exactly which tables, columns, and migration files were created.

Inputs

Input	Source	Description
completedAgent	domain-invoker	Name of the domain agent that just finished
agentOutput	domain-invoker	Raw output and file list from the domain agent's run
ticket	ticket-fetch	Story ticket for context

Extraction Strategy

Use Glob and Read tools to scan files written or modified during the domain agent's run. Extract domain-specific signals by file type and content pattern.

DB Agent Artifacts (db-coding-agent)

Scan: migration files (migrations/*.sql, **/migrations/**), ORM model files, schema files.

Extract:

• New/modified table names — from CREATE TABLE, ALTER TABLE statements or model class names
• Column names and types — from DDL or model field definitions
• Migration file paths — exact paths to migration files written
• New indexes — from CREATE INDEX statements
• Foreign key relationships — from REFERENCES clauses or FK decorators
• Summary sentence — e.g. "Created table user_sessions with 4 columns. Migration: migrations/20260324_add_user_sessions.sql."

Backend Agent Artifacts (backend-coding-agent)

Scan: route files, controller files, service files, DTO/schema files.

Extract:

• New API endpoint URLs — from route definitions (@Get('/path'), router.get('/path'), app.get('/path'))
• HTTP methods — from route decorators or method calls
• Request/response shapes — from DTO class fields or schema definitions
• Service interface names — from exported class/interface names in service files
• New environment variables — from process.env.* or config references
• Summary sentence — e.g. "Added POST /auth/login and GET /auth/me endpoints. AuthService with validateCredentials method."

Frontend Agent Artifacts (frontend-coding-agent)

Scan: component files, page files, route config files, state management files.

Extract:

• New component names — from export function ComponentName or export default
• New routes — from route config objects or file-system routing paths
• New state keys — from Redux slice names, Zustand store keys, Context names
• Prismatic components used — from imports of @Vensure-Devops-QA/prismatic-*
• Summary sentence — e.g. "Added LoginPage component at /login route. Uses AuthContext for session state."

DevOps Agent Artifacts (devops-coding-agent)

Scan: pipeline YAML files, Dockerfile, .env.example files.

Extract:

• Pipeline file paths modified — exact paths
• New environment variables added — from pipeline env blocks or .env.example
• New build stages — from Dockerfile stage names
• Registry push targets — from pipeline push steps
• Summary sentence — e.g. "Updated .github/workflows/ci.yml with SESSION_TABLE env var. Added Snyk scan stage."

Security Agent Artifacts (security-coding-agent)

Scan: middleware files, auth files, validation files, audit log files.

Extract:

• Security findings resolved — from code comments or commit messages referencing CVE/finding IDs
• New input validation contracts — from validation schema definitions
• Auth middleware added — from middleware export names
• Summary sentence — e.g. "Added JwtAuthMiddleware. Resolved SQL injection finding in UserRepository.findByEmail."

Fallback

If file scanning cannot produce structured artifacts (e.g., agent wrote no files, or output is purely in-memory), use the agent's text output as the summary directly, prefixed with "(unstructured)".

Output

{
  "agent": "db-coding-agent",
  "summary": "Created table `user_sessions` with columns: id (UUID PK), user_id (FK → users.id), token (VARCHAR 512), expires_at (TIMESTAMP). Migration: migrations/20260324_add_user_sessions.sql.",
  "artifacts": [
    "migrations/20260324_add_user_sessions.sql",
    "src/models/UserSession.ts"
  ],
  "contextForNext": "The next agent should reference `user_sessions` table for JWT session storage. FK constraint on `users.id` is enforced at the DB layer. Column names: id, user_id, token, expires_at."
}

Field Reference

Field	Description
agent	Name of the domain agent that produced these artifacts
summary	One or two sentence human-readable summary of what was implemented
artifacts	Relative paths of files written or materially modified during this agent's run
contextForNext	Explicit instructions for the next agent referencing concrete names (table names, endpoint URLs, component names) produced by this agent

The contextForNext field is what gets injected into the next agent's completedAgents[] entry. It must contain concrete names — not vague descriptions — so the downstream agent can reference them directly in its implementation.