project-adopt
project-adopt brings an established codebase into the Specification-Driven Development workflow by detecting existing code and documentation, inferring the domain, and scaffolding the 8-layer artifact structure. It reverse-engineers baseline artifacts from your running system at draft status, seeding the SDD backbone in one setup pass. Hand off to doc-flow and per-layer audits to close gaps and promote drafts to ready.
project-adopt onboards existing codebases into the SDD workflow by reverse-engineering baseline artifacts from your running system.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
project-adopt onboards existing codebases into the SDD workflow by reverse-engineering baseline artifacts from your running system. project-adopt brings an established codebase into the Specification-Driven Development workflow by detecting existing code and documentation, inferring the domain, and scaffolding the 8-layer artifact structure. It reverse-engineers baseline artifacts from your running system at draft status, seeding the SDD backbone in one setup pass. Hand off to doc-flow and per-layer audits to close gaps and promote drafts to ready.
Use it when
- project-adopt scaffolds the full 8-layer documentation structure for brownfield projects.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
vladm3105/aidoc-flow-framework/project-adopt · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I adopt an existing codebase into the SDD workflow?
project-adopt brings your established codebase into Specification-Driven Development by detecting existing code and documentation, then inferring your domain and scaffolding the complete 8-layer artifact structure. It reverse-engineers baseline artifacts from your running system at draft status, seeding the SDD backbone in one setup pass so you can hand off to doc-flow and per-layer audits.
What does project-adopt do for brownfield project setup?
project-adopt scaffolds the full 8-layer documentation structure for brownfield projects, automating the reverse-engineering of baseline artifacts from your existing codebase. It detects code patterns, infers your domain, and generates draft SDD artifacts without manual baseline creation, letting you focus on layer audits and gap closure.
Can project-adopt reverse engineer baseline artifacts from code?
Yes. project-adopt analyzes your running system to detect code, infer domain context, and generate draft baseline artifacts automatically. These reverse-engineered artifacts seed your SDD backbone at draft status, ready for promotion to ready once doc-flow and per-layer audits validate and close any gaps.
How does project-adopt migrate legacy code to the SDD framework?
project-adopt migrates legacy projects to SDD by performing one-time automated baseline generation from your existing codebase. It initializes the SDD documentation backbone, converts your running system into the framework structure, and prepares draft artifacts for layer-by-layer audits and refinement.
What is the one-time setup process for SDD on an existing project?
project-adopt sets up the SDD backbone for already-built projects in a single pass: it detects your code, infers domain, scaffolds all 8 layers, and reverse-engineers draft baseline artifacts from your running system. After this one-time initialization, hand off to doc-flow and audits to promote drafts to ready status.
Is project-adopt open source and what license does it use?
project-adopt is released under the MIT license, making it free to use, modify, and distribute in both open-source and commercial projects.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
project-adopt
Purpose
Onboard an existing codebase (brownfield) into the SDD flow: detect the
current code and any docs, infer the domain, scaffold the 8-layer docs/
structure, and reverse-engineer baseline artifacts from the code at
draft status — the one-time setup that gives a running system its SDD
backbone. It is the brownfield counterpart to ../project-init/SKILL.md.
Layer: cross-cutting utility (precedes BRD).
When to Use
The greenfield/brownfield boundary is the deciding factor:
Use project-adopt when (brownfield):
- Source code already exists, but there is no
(truncated - see the full file via the links below)
File tree — 1 file
platforms/claude-code-plugin/skills/project-adopt/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Adopt an existing codebase into the SDD workflow with reverse-engineered baseline artifacts”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Quality-advisor gives live feedback while you create or review SDD documents, catching completion gaps, documentation anti-patterns, tag compliance, and naming issues before submission. It scores sections, detects common problems like missing traceability or broken links, validates cumulative tagging across layers, and returns actionable recommendations to fix issues.
doc-tdd generates Layer 7 TDD artifacts that translate component contracts into concrete test cases with quality thresholds. It maps BDD scenarios to unit, integration, functional, and end-to-end tests, establishes coverage targets per type, and sequences the Red-Green-Refactor workflow before implementation begins.
doc-validator enforces consistency rules across your entire SDD documentation corpus—catching broken links, orphaned artifacts, cumulative-tag gaps, duplicate IDs, and traceability gaps across all 8 layers. It runs declarative checks against your corpus structure and can optionally repair safely-fixable issues like missing reciprocal links or stale metadata. Use it before releases or after batch generation to ensure your documentation chain stays machine-verifiable and traceable.
doc-bdd translates EARS requirements into Layer 4 acceptance scenarios using structured YAML (not Gherkin), each with Given-When-Then phases, element-level trace links to upstream EARS, and forward mapping to SPEC sections. Use this after EARS is complete and before ADR/SPEC authoring; for batch generation across multiple documents, the autopilot skill handles orchestration.
doc-adr captures a single architectural decision using the Context-Decision-Consequences pattern, positioned as Layer 5 in the specification-driven development flow. It records the rationale, chosen approach, evaluated alternatives, and accepted trade-offs for decisions that bridge container and component design.
migrate helps you add govctl governance to an established project by examining existing evidence—documentation, code structure, VCS history, and configuration—to recover consequential decisions and specifications. It guides you through a discovery phase, presents candidates for backfill as Architecture Decision Records, RFCs, or Work Items, and executes only authorized changes in small coherent batches. The workflow preserves traceability, respects existing artifact state, and stops when evidence conflicts or authorization is unclear.
More skills doc-prd (MIT)