FullSpecFullSpec
FullSpec Method · the open methodology

Your AI coding tool
doesn't know your company.

It has access to your code. It does not have access to your context. The FullSpec Method turns your scattered knowledge into phase-specific specs that any AI agent can execute — Cursor, Claude Code, Copilot.

$ npx fullspec init
Works withCursorVS CodeClaude CodeCopilotCodex
The context gap

Your company's knowledge
is scattered.

Your AI tools see your repo. They don't see the Jira ticket that drove the feature, the ADR that shaped the architecture, the design system the team actually uses, or the QA standard that gates a merge.

“95% of IT leaders identify data fragmentation as the primary AI bottleneck.”

Jira ticketsConfluence pagesSlack threadsCodebase patternsDesign systemADRsSales decksQA playbooks
# .fullspec/spec.md
Feature: Order export · grounded in JIRA-1843, ADR-019, design tokens v3
How it works

Context in. Specs out.

FullSpec sits between your company's knowledge and whatever AI tools your team uses. It produces the missing layer: phase-specific contextual specs.

01 · Your context

Configure your sources

Plug in Jira, Confluence, your codebase, design system, ADRs, sales/CS decks, QA playbooks — only what you need.

02 · FullSpec

Modes generate specs

Each SDLC phase has a specialized mode that ingests focused context and outputs a markdown spec — one document per phase.

03 · Your agent

Cursor, Claude Code, Copilot

Your AI coding agent reads the spec and produces code that looks like your team wrote it. Same agent. Better output.

The modes

Each phase gets the right context.

One mode per SDLC phase. One spec document per mode. Each ingests a focused slice of your company's knowledge — never the whole firehose. Customizable to your standards.

IdeaPhase 01

Frame the problem

Turns a vague request into a structured problem statement grounded in customer signal.

Customer ticketsCS notesSales decks
SpecPhase 02

Define what you're building

Generates a PRD using your strategy docs, prior PRDs, and existing product context.

PRDsStrategy docsRoadmap
PlanPhase 03

Architect how to build it

Produces an architecture brief that respects your ADRs, services, and tech standards.

CodebaseADRsService map
UXPhase 04

Design in your language

Drafts UX in your design system — your tokens, your components, your patterns.

Design systemFigma tokensExisting screens
Build→ Your agent

Hand off to your agent

FullSpec stops here. Cursor, Claude Code, or Copilot reads the spec and writes the code.

CursorClaude CodeCopilot
TestPhase 06

Test the right surface

Test plan grounded in your QA standards, coverage targets, and risk register.

QA playbookTest matrixRisk register
GuardPhase 07

Security in your framework

Compliance + threat checklist mapped to your security framework, not OWASP boilerplate.

SOC2Threat modelSec policy
ShipPhase 08

Deployment runbook

Rollout plan in your stack — feature flags, observability, rollback, oncall handoff.

InfraRunbooksOn-call
SellPhase 09

GTM grounded in your ICP

Launch brief: positioning, landing copy, internal enablement — using your sales motion.

ICPPricingSales decks

Each mode is configurable. Your QA team adds their test matrix. Your security team adds their compliance framework. Your design team plugs in their tokens. No two FullSpecs are alike.

Brownfield superpower

Specs in YOUR language.

FullSpec reads your existing codebase, design system, and architecture patterns. Generated specs reference your real components, your conventions, your API patterns — not generic boilerplate.

When Cursor reads that spec, it produces code that looks like your team wrote it.

  • Reads your design tokens, not Tailwind defaults
  • References YOUR API client, not axios examples
  • Follows YOUR test conventions, not generic Jest stubs
  • Honors YOUR ADRs, not generic best practices
📝.fullspec/spec.md
# Feature: Multi-tenant order export

## Source context
- JIRA-1843 (Acme + Northwind quarterly close)
- ADR-019: tenant isolation via row-level security
- Design tokens v3.2 (use tokens.spacing.lg)

## API surface
Use existing apiClient.orders.export()
not a new fetch wrapper. Pagination follows
the established cursor pattern from
/orders/list.ts.

## UI
Compose from <DataGrid> + <ExportSheet>.
Do not introduce a new modal primitive.

## Tests
Follow tests/orders/*.spec.ts
factory + scenario + assertion.
Context compounds

Every feature makes your AI smarter.

FullSpec specs are markdown files in your repo. They version with your code. The library grows. Your context becomes IP that competitors cannot copy.

10
features in

Architectural patterns are captured. Specs reference real ADRs.

50
features in

Design language, testing philosophy, and API conventions are encoded.

100
features in

A new engineer — or a new agent — builds as if they've been on the team for years.

Start in one command.

FullSpec runs locally. Specs live in your repo. No API keys required to start.

$ npx fullspec init

Don't want to build it yourself? Have FullSpec Studio ship it for you in 5 days →