classify-product-state

Name: classify-product-state
Availability: InStock
Author: KOHLEX

Classify product repositories into Brownfield levels 0-3 and output structured JSON.

Updated Jun 4, 2026

Search Tags:#automation #planning #onboarding #codebase #json #brownfield #classify

Ready to run

npx skills add https://github.com/Kohlex/autopilot-plugin --skill classify-product-state

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: classify-product-state
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/classify-product-state
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill classify-product-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly determine the Brownfield level of a product repository by analyzing planning artifacts and codebase signals, without mutating the inspected repo.

Core Features & Use Cases

Inspects a product slug and optional repo path to emit a Level 0/1/2/3 JSON state-vector.
Determines the recommended entry point (platform-init, autopilot, or brownfield-onboard) based on Brownfield signals.
Supports guidance for planning and onboarding workflows within AutoPilot's Brownfield framework.

Quick Start

Invoke classify-product-state with a product slug (and optional repo path) to produce the brownfield state JSON.

Frequently Asked Questions about classify-product-state

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

FAQPage Schema

How do I determine the brownfield level of an existing codebase?▼

Brownfield levels 0-3 indicate the maturity of an existing product codebase, ranging from minimal code to complex established systems. Classifying this level helps determine the recommended entry point for onboarding and automation workflows.

How do I classify a product repository for onboarding automation?▼

You can classify a product repository for onboarding automation by invoking the classification process using a product slug and an optional repo path. It reads planning signals and returns a structured JSON with a recommended action without mutating the repository.

Does the brownfield classification process modify my repository files?▼

The brownfield classification process does not modify your repository files. It safely reads planning and codebase signals to output a structured JSON state-vector, ensuring the inspected repository remains completely unmutated.

What is the recommended entry point for a level 2 brownfield codebase?▼

For a level 2 brownfield codebase, the recommended entry point is determined by analyzing specific codebase signals. The classification outputs a structured JSON suggesting either platform-init, autopilot, or brownfield-onboard based on the detected maturity.

Can I use a product slug without a repo path to classify brownfield state?▼

You can use a product slug without a repo path to classify brownfield state. The classification process accepts the slug as required input and uses optional repo path data to generate the structured JSON state-vector.