project-init

Detect tech stacks and generate crew-config.json for project initialization.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/gridi-ai/gridi-skills --skill project-init-gridi-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-init
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/project-init
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill project-init-gridi-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Project initialization and configuration can be time-consuming and error-prone when bootstrapping new repositories or reconfiguring existing ones. This skill automates tech-stack detection and generates a standardized crew-config.json to accelerate setup and reduce drift.

## Core Features & Use Cases

  • Auto-detects framework, language, database, and conventions from existing projects.
  • Interactive setup flow for new projects with guided questions when no code is present.
  • Generates a ready-to-use crew-config.json with sensible defaults and project-wide policies.
  • Provides a reconfiguration path to re-analyze and apply updated settings.

### Quick Start Run the skill at the project root to generate crew-config.json and initialize the workflow.

Frequently Asked Questions about project-init

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

FAQPage Schema
How do I auto-detect a tech stack and generate a project configuration file?

To auto-detect a tech stack and generate configuration, run the initialization workflow at your project root. It automatically analyzes existing code to identify frameworks and languages, then outputs a standardized crew-config.json file with sensible defaults.

Can I set up project configuration interactively when there is no source code?

Yes, you can set up project configuration interactively without source code. The workflow provides a guided interactive setup flow with prompts and optional presets to help you manually define your tech stack and generate crew-config.json.

What is the best way to reconfigure an existing repository's workflow settings?

The best way to reconfigure workflow settings is to run the initialization skill again at the project root. It provides a reconfiguration path that re-analyzes your existing codebase and applies updated settings to your crew-config.json file.

Does project initialization work for both new projects and existing repositories?

Yes, project initialization works for both new projects and existing repositories. It applies auto-analysis to detect conventions when code exists, and uses an interactive setup flow with guided questions when no source is present.

What are the limitations of auto-detecting framework and database conventions?

A limitation of auto-detecting conventions is that it requires an existing project root to analyze. Without source code present, the auto-detection mechanism cannot infer your framework or database, requiring manual interactive setup instead.