aidlc-workspace-detection

Scan development workspaces to detect greenfield or brownfield project types.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-workspace-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-workspace-detection
Source: https://github.com/bluejayA/devflow-aidlc-like/tree/main/skills/aidlc-workspace-detection
Command: npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-workspace-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically analyzes your current development workspace to determine if you are starting a new project (Greenfield) or working with an existing codebase (Brownfield), setting the stage for the AI-DLC workflow.

Core Features & Use Cases

  • Project Type Detection: Accurately identifies whether a workspace is Greenfield or Brownfield based on file presence and Git history.
  • Technology Stack Analysis: For Brownfield projects, it scans manifest files (package.json, go.mod, etc.) to identify the programming language, frameworks, and key dependencies.
  • Code Structure Assessment: For Brownfield projects, it analyzes the directory layout and identifies potential architectural patterns (e.g., MVC, Layered).
  • Use Case: When you initiate a new development task, this Skill quickly tells you if you need to set up a new project structure or if you're diving into an existing one, and provides an initial overview of the existing tech stack.

Quick Start

Run the aidlc-workspace-detection skill to analyze the current project directory.

Frequently Asked Questions about aidlc-workspace-detection

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

FAQPage Schema
How do I detect if my workspace is a greenfield or brownfield project?

To detect if a workspace is greenfield or brownfield, scan the directory for existing manifest files and Git history. This skill analyzes file presence and directory patterns to determine project status and identify the technology stack.

How does technology stack detection work for existing codebases?

Technology stack detection works by scanning manifest files like package.json or go.mod. This identifies programming languages, frameworks, and key dependencies to provide an initial overview of the existing codebase architecture.

Can I identify architectural patterns by analyzing directory layout?

Yes, you can identify potential architectural patterns by analyzing the directory layout. This skill assesses code structure for brownfield projects to map out layouts and detect patterns like MVC or Layered architecture.

What is the best way to assess code structure before starting a development task?

The best way to assess code structure is to run an automated workspace analysis. This skill evaluates the directory layout and manifest files to provide a comprehensive project assessment as the first stage of the INCEPTION phase.

Does this workspace detection require Git history to determine project type?

Workspace detection does not strictly require Git history but uses it to accurately identify project type. It analyzes both manifest file presence and Git history to determine if you are working with an existing codebase or starting new.