Engineering Docs

22 composable, auto-triggering skills that turn your coding agent into a principal engineer - from raw idea to production-ready documentation.

---

Why Engineering Docs?

Your coding agent is powerful, but it doesn't know your project's architecture, your users, or your constraints. Engineering Docs gives it principal-level documentation skills — so it can:

• Turn raw ideas into complete blueprints — business concept → technical spec → architecture → deployment plan
• Ask the right questions — tool-call interviews with 2-3 targeted questions per skill (no repeated questions)
• Generate production-ready documents — ISO/IEC/IEEE 29148, C4 Model, STRIDE, Google SRE standards
• Work across 14+ agents — Claude Code, Copilot, Cursor, Gemini CLI, Goose, Pi, and more

---

How It Works

The plugin works through a structured workflow:

1. User gives idea → Orchestrator skill activates automatically
2. Mode detection → Greenfield (new) vs Brownfield (existing)
3. Interview phase → Tool-call questions with context loading
4. Document generation → Sequential generation with 22 specialized skills
5. Consistency checks → Cross-document verification
6. Master index → Complete blueprint ready for implementation

---

Quickstart

npx engineering-docs

Or install for your specific agent:

Agent	Install Command
Claude Code	/plugin marketplace add fattain-naime/engineering-docs/plugin install engineering-docs@engineering-docs
Gemini CLI	gemini extensions install https://github.com/fattain-naime/engineering-docs
Cursor	npx engineering-docs --cursor
Goose	npx engineering-docs --goose
Pi	npx engineering-docs --pi
OpenCode	npx engineering-docs --opencode
Kilo Code	npx engineering-docs --kilo
Roo Code	npx engineering-docs --roo
Cline	npx engineering-docs --cline
Kimi Code	/plugins install https://github.com/fattain-naime/engineering-docs
Codex	npx engineering-docs --codex
Copilot CLI	npx engineering-docs --copilot
Factory Droid	npx engineering-docs --factory

See Installation for detailed instructions.

---

How It Works

graph LR
    A[Your Idea] --> B[Orchestrator]
    B --> C[Interview]
    C --> D[Business Concept]
    D --> E[Project Plan]
    E --> F[Technical Spec]
    F --> G[System Architecture]
    G --> H[API Design]
    H --> I[Implementation Plan]
    I --> J[Test Strategy]
    J --> K[Deployment Plan]
    K --> L[Master Index]

1. Give it your idea — "I want to build X"
2. Answer 2-3 questions per skill — via tool calls, not inline chat
3. Review each document — approve or request changes
4. Get your blueprint — complete, cross-consistent documentation set

Smart features:

• Context loading — reads prior documents before asking questions (never repeats)
• Tool-call interviews — clean input capture, no conversation pollution
• Right-sizing — skips documents that don't apply to your project
• Cross-document consistency — verifies entity names, roles, decisions match

---

What's Inside

Skills Library (22 Skills)

Discovery & Planning

Skill	What It Produces
using-engineering-docs	Orchestrator — routes to all other skills automatically
business-concept	Problem, users, value proposition, monetization, constraints
project-plan	Scope, milestones, RACI, timeline, work breakdown
user-personas-behavior	User personas, JTBD, success metrics, analytics plan

Specification & Feasibility

Skill	What It Produces
technical-specification	SRS/TSD with EARS syntax, traceability matrix
technical-feasibility-study	Go/no-go recommendation with evidence

Architecture & Design

Skill	What It Produces
system-architecture-document	C4 diagrams, 4+1 views, tech stack, NFRs
architecture-decision-record	Immutable ADR log (MADR format)
database-design-document	ERD, schema, indexing, migration plan
api-design-document	REST/OpenAPI 3.1 contract, RFC 7807 errors
admin-access-control-specification	RBAC matrix, audit logging, break-glass
technical-blueprint	Google/Stripe-quality TDD per feature
ux-flow-specification	User journeys, screen flows, UI states
design-system-specification	Design tokens, components, accessibility

Quality & Risk

Skill	What It Produces
security-threat-model	STRIDE analysis, attack surface, mitigations
test-strategy-document	Testing pyramid, CI gates, coverage targets
implementation-plan	Dependency-ordered build sequence, phase gates

This is the beginning of the README. Read the rest at the original. Read the full README ↗