Stack, Dev Lifecycle, Infrastructure & Governance (Streams E–H)
Streams E through H cover the broader development ecosystem — stack decisions, agent generation, tooling, git integration, multi-agent orchestration, and governance.
Stream E — Stack & Agents
suggest_stack
Suggest a technology stack based on project requirements.
When to use: At project inception when the team is choosing between competing technologies, or when validating a stack choice against project constraints.
Prompt: "Suggest a stack for a real-time collaborative document editor for project proj_abc123"check_versions
Check dependency versions for updates, deprecations, and security issues.
What it checks:
- Current vs latest stable versions
- Known CVEs and security advisories
- Deprecated packages
- Breaking change warnings for major version gaps
Prompt: "Check dependency versions for project proj_abc123"generate_skill
Generate an agent skill file for a specific AI coding agent platform.
Supported platforms: Claude Code (CLAUDE.md skills), Cursor (.cursorrules fragments), Windsurf, Copilot instructions, custom agent definitions.
Prompt: "Generate a Claude Code skill for the authentication workflow in project proj_abc123"detect_agent
Detect the AI coding agent platform in use at the project path.
When to use: When you need to generate agent-specific artifacts (rules files, skills, memory files) and want SpecForge to auto-select the right format.
Prompt: "Detect what AI agent is configured at /Users/me/my-app"generate_sub_agent
Generate a sub-agent definition for multi-agent orchestration.
What it produces: A structured agent definition with capabilities, resource ownership, handoff protocol, and communication contract — ready for use with orchestrate_agents.
Prompt: "Generate a sub-agent for the database migration task in spec SPEC-011 for project proj_abc123"generate_rules
Generate agent rules files — .cursorrules, CLAUDE.md, Copilot instructions, Windsurf rules — from the project's Constitution and detected patterns.
Prompt: "Generate a CLAUDE.md for project proj_abc123"
Prompt: "Generate .cursorrules for project proj_abc123"Stream F — Dev Lifecycle
suggest_tooling
Assess and suggest dev lifecycle tooling across the full stack.
Coverage:
- CI/CD (GitHub Actions, GitLab CI, CircleCI, etc.)
- Testing (unit, integration, E2E, visual regression)
- Monitoring and observability (OpenTelemetry, Datadog, Grafana)
- AI-native tooling (LLM observability, semantic cache, prompt management, guardrails)
- Frontend performance tooling (Lighthouse CI, visual regression, component libraries)
Prompt: "Suggest tooling for project proj_abc123"generate_tests
Generate a test plan and test file stubs from a spec's acceptance criteria.
What it produces:
- Test plan with test case names mapped to acceptance criteria
- Test file stubs in your project's test framework (vitest, pytest, go test, JUnit, etc.)
- Coverage targets per criterion
- Mocking strategy for external dependencies
Prompt: "Generate tests for spec SPEC-003 in project proj_abc123"generate_docs
Generate documentation from specs and code — API docs, README sections, architecture overviews.
Prompt: "Generate API documentation for spec SPEC-007 in project proj_abc123"
Prompt: "Generate a README section for the authentication module from spec SPEC-001"integrate_pm
Integrate with project management tools — create issues, epics, or tasks from specs.
Supported: Jira, Linear, GitHub Issues, GitLab Issues, Trello, Notion.
Prompt: "Create a GitHub issue for spec SPEC-004 in project proj_abc123"
Prompt: "Create a Linear task for spec SPEC-009 in project proj_abc123"Stream G — Infrastructure
manage_context
Save, load, and manage persistent context notes across sessions.
When to use: When you need to preserve important architectural decisions, external constraints, or team agreements that aren't captured in specs.
Prompt: "Save context: we decided to use Postgres 16 with pgvector for all AI features in project proj_abc123"
Prompt: "What context have we saved for project proj_abc123?"manage_git
Git integration — create branches, generate PR descriptions, changelogs, and hooks linked to specs.
Prompt: "Create a branch for spec SPEC-005 in project proj_abc123"
Prompt: "Generate a PR description for spec SPEC-005 in project proj_abc123"
Prompt: "Generate a changelog from specs SPEC-001 through SPEC-010 for project proj_abc123"orchestrate
Multi-agent orchestration — register agents, lock resources, distribute tasks, coordinate parallel execution.
Prompt: "Register an agent for spec SPEC-011 and lock the auth module in project proj_abc123"consult_docs
Consult framework documentation for a specific topic — fetches and summarizes relevant docs without leaving your conversation.
Prompt: "Consult React docs about concurrent rendering for project proj_abc123"
Prompt: "What does the FastAPI docs say about dependency injection?"discover_mcps
Discover MCP servers configured in the current environment.
Prompt: "What MCP servers are available in my environment?"suggest_mcps
Suggest MCP servers that would benefit the project based on its stack and detected patterns.
Prompt: "Suggest MCP servers for project proj_abc123"migrate_tech
Guide tech stack migration — analyze source codebase, map equivalences, generate migration plan, validate functional parity, and plan DB migration.
When to use: When moving from one framework to another (Express → Fastify, Django → FastAPI, Create React App → Vite), upgrading a major dependency, or migrating databases.
Prompt: "Plan a migration from Express to Fastify for project proj_abc123"
Prompt: "Migrate from class-based to functional React components in project proj_abc123"orchestrate_agents
Declare agent capabilities, route tasks to the best agent, generate structured handoff contexts, and detect file-ownership conflicts before parallel execution.
Prompt: "Orchestrate agents for specs SPEC-012, SPEC-013, SPEC-014 in project proj_abc123"validate_workflow
Validate developer workflow conventions — AI model selection, Git Flow compliance, MCP tool conventions, or full workflow audit.
Prompt: "Validate my workflow for project proj_abc123"
Prompt: "Check Git Flow compliance for project proj_abc123"log_decision
Register, list, search, or supersede architectural and process decisions for a project.
When to use: Lightweight alternative to full ADRs for process decisions, tool choices, or team agreements.
Prompt: "Log decision: we will use pnpm as the package manager for all new projects"
Prompt: "List all decisions for project proj_abc123"facilitate
Entry point for users unfamiliar with SpecForge — guides them through the SDD workflow interactively.
When to use: When onboarding a new team member or when someone is using SpecForge for the first time.
Prompt: "Facilitate a SpecForge session for my project at /Users/me/my-app"request_context
Generate a prompt that asks the user for reference documentation (README, PRD, architecture docs) to enrich the project knowledge base.
Prompt: "Request context for project proj_abc123"contribute_context
Persist structured knowledge extracted from user-provided documents into the project knowledge base.
Prompt: "Contribute the attached PRD document to project proj_abc123"Stream H — Governance & Stack Health
data_governance
Detect PII in specs, generate retention policies, draft privacy notices, and audit GDPR/CCPA/LGPD compliance.
When to use: Before any spec that handles user data — sign-up flows, profile management, analytics, or data exports.
Prompt: "Run a data governance check on spec SPEC-006 for project proj_abc123"
Prompt: "Generate a GDPR compliance audit for project proj_abc123"audit_stack
Audit all project dependencies — classifies as up_to_date, outdated, vulnerable, or unmaintained. Generates a StackHealthScore (0–100).
When to use: Periodically (monthly or before each release) to keep the dependency graph healthy.
Prompt: "Audit the stack for project proj_abc123"plan_upgrade
Generate a migration plan for upgrading a specific package — breaking changes, estimated effort, and rollback procedure.
Prompt: "Plan the upgrade from React 18 to React 19 for project proj_abc123"
Prompt: "Plan upgrading Zod from v3 to v4 in project proj_abc123"detect_deprecations
Scan project source files for deprecated API patterns (no network required) and return a deprecation report with tech-debt estimate.
When to use: Before a major version upgrade, or as part of a quarterly tech debt review.
Prompt: "Detect deprecated APIs in project proj_abc123"check_config_health
Analyze project configuration files for misconfigurations, missing fields, and best-practice violations across all ecosystems.
What it checks:
- Package manager config (package.json, pyproject.toml, go.mod, Cargo.toml, etc.)
- TypeScript/Python/Go/Rust compiler settings
- CI/CD pipeline configuration
- Linter and formatter settings
When to use: After project setup, during onboarding, or when builds fail for configuration reasons.
Prompt: "Check config health for project proj_abc123"