agentpit-init

Initialize AgentPit feature modules and generate .agentpit/state.json.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/hangeaiagent/agentpit-Skills --skill agentpit-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentpit-init
Source: https://github.com/hangeaiagent/agentpit-Skills/tree/main/skills/agentpit-init
Command: npx skills add https://github.com/hangeaiagent/agentpit-Skills --skill agentpit-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initializes AgentPit new feature modules by collecting the feature name, route group, and permission requirements, and by generating the .agentpit/state.json to drive subsequent development steps.

Core Features & Use Cases

  • Environment validation ensures you are at the AgentPit project root by checking for prisma/schema.prisma, lib/auth.ts, app/ directory, and package.json.
  • Interactive data collection uses AskUserQuestion to gather a kebab-case feature name and a concise description.
  • Automatic classification of feature type (user page, marketing page, API, or admin) with appropriate default permissions and routing setup, plus optional Prisma model definitions.
  • Generates a ready-to-use .agentpit/state.json containing the feature configuration, routing group, authentication requirements, and planned API routes.

Quick Start

Run the initialization flow to collect the feature details and generate the .agentpit/state.json.

Frequently Asked Questions about agentpit-init

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

FAQPage Schema
How do I initialize a new feature module in an AgentPit project?

You need an AgentPit project root containing prisma/schema.prisma, lib/auth.ts, the app/ directory, and package.json. The environment validation step checks for these specific files before allowing feature module initialization to proceed.

What configuration does the AgentPit state.json feature setup include?

The state.json configuration includes the kebab-case feature name, classified feature type, routing group, authentication requirements, planned API routes, and optional Prisma model definitions needed for subsequent development steps.

How does feature module initialization handle routing groups and permissions?

Feature module initialization automatically classifies the feature type as a user page, marketing page, API, or admin module, then applies appropriate default permission requirements and routing group setup based on that classification.

Can I define Prisma models when setting up a new AgentPit feature?

Yes, you can define optional Prisma model definitions during the interactive data collection phase, which are then included in the generated .agentpit/state.json to drive subsequent database schema development steps.