adopt

Scan a codebase and scaffold QuangFlow governance artifacts with a CONTEXT.md.

6|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/DuongMQuang/quangflow --skill adopt-duongmquang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/DuongMQuang/quangflow/tree/main/plugins/quangflow/skills/adopt
Command: npx skills add https://github.com/DuongMQuang/quangflow --skill adopt-duongmquang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboards an existing codebase into QuangFlow by scanning the repository, scaffolding the required directory structure, and generating a reviewed CONTEXT.md for downstream phases.

Core Features & Use Cases

  • Automated repository discovery and scanning to infer tech stack and project structure.
  • Automated scaffolding of QuangFlow's directory layout to prepare for governance.
  • Generation of a reviewed CONTEXT.md with decision records and plan alignment for downstream phases.
  • Excellent for teams migrating legacy projects into a structured, auditable workflow.

Quick Start

Run the adopt workflow on your project to begin scanning, scaffolding, and generating the CONTEXT.md for governance.

Frequently Asked Questions about adopt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard an existing codebase into a structured workflow?▼

To onboard an existing codebase, you scan the project to infer the tech stack, scaffold the necessary directory structure, and generate a reviewed CONTEXT.md for downstream phases. This process prepares legacy projects for structured, auditable governance.

What is a CONTEXT.md file and when do I need it for project governance?▼

A CONTEXT.md file is a governance artifact that captures decision records, project structure, and plan alignment for downstream phases. You need it when migrating legacy projects into a structured workflow to ensure locked decisions and a reusable memory footprint.

How do I automate scaffolding the directory structure for a legacy codebase?▼

You automate scaffolding by running a staged pipeline that scans the repository, extracts features, and generates the required directory layout. This prepares the project for governance by automatically aligning the existing structure with required artifacts.

Can I use this to migrate legacy projects without manually mapping the tech stack?▼

Yes, you can migrate legacy projects without manual mapping because the workflow coordinates specialized subagents to automatically infer the tech stack and project structure. It outputs a file map and locked decisions for review.

What's the best way to generate decision records for an existing repository?▼

The best way to generate decision records is through a scanner to doc generator pipeline that analyzes the repository and scaffolds governance artifacts. This produces locked decisions and a draft CONTEXT.md for review.

Does onboarding an existing codebase require specific dependencies?▼

Onboarding an existing codebase requires no specific external dependencies. The workflow uses a staged internal pipeline of scanner, feature extractor, doc generator, and scaffolder to analyze the repository and generate necessary governance artifacts.