setup

Detect repository state and install prerequisites for standards-based setup.

2|Updated May 19, 2026
One-click install
npx skills add https://github.com/element22llc/e22-plugins --skill setup-element22llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/element22llc/e22-plugins/tree/main/plugins/steer/skills/setup
Command: npx skills add https://github.com/element22llc/e22-plugins --skill setup-element22llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of getting a repository onto engineering standards, automatically determining the appropriate setup path based on the repository's state.

Core Features & Use Cases

  • Automated State Detection: Detects the state of the repository's spec spine and routes to the correct setup path (greenfield init, brownfield adopt, or steady-state sync).
  • Prerequisite Installation: Installs necessary prerequisites if the toolchain is missing before executing the setup path.
  • User-Friendly Interface: Provides a single entry point for setup, making it easy to onboard new repositories or sync existing ones.

Quick Start

Use the setup skill to initialize a new repository following the engineering standards.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I automate repository setup to meet engineering standards?

Automating repository setup to meet engineering standards is achieved by detecting the repository's state and routing it to the correct setup path, ensuring adherence to required engineering guidelines.

What is the best way to onboard an existing repository to new engineering standards?

Onboarding an existing repository to new engineering standards uses automated state detection to identify a brownfield adopt path, applying the necessary configurations without disrupting current workflows.

How does state detection work when bootstrapping a repository toolchain?

State detection works when bootstrapping a repository toolchain by inspecting the spec spine to determine whether to execute a greenfield init, brownfield adopt, or steady-state sync path.

Do I need to manually install prerequisites before initializing a new repository?

You do not need to manually install prerequisites before initializing a new repository, because the setup process automatically detects missing toolchain components and installs them before executing.

Can I use this automated setup for both new and existing repositories?

You can use this automated setup for both new and existing repositories, as it provides a single entry point that applies engineering standards regardless of the current repository state.

What are the limitations of automated engineering standards detection for repository bootstrap?

A limitation of automated engineering standards detection during repository bootstrap is that it strictly routes setup paths based on the detected spec spine condition, requiring a valid repository state to function correctly.