engineering-kernel

Bootstrap or audit agent-led engineering workflows with policy YAML and template files.

2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/alexxety/agent-engineering-kernel --skill engineering-kernel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-kernel
Source: https://github.com/alexxety/agent-engineering-kernel/tree/main
Command: npx skills add https://github.com/alexxety/agent-engineering-kernel --skill engineering-kernel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the need to re-explain engineering workflows from chat memory for every new agent or repository. It provides a universal, reusable kernel that establishes PRD-first execution, GitHub issue decomposition, verification discipline, and multi-agent coordination rules that work across GPT/Codex and Claude-style agents.

Core Features & Use Cases

  • Project Bootstrap: Materialize a complete engineering operating system into any repository, including AGENTS.md, CONTRIBUTING.md, issue templates, PR templates, and label sync scripts.
  • Workflow Canon Enforcement: Enforce PRD-first execution, research policy, bug intake, kernel sync review, and session issue sync closeout without relying on chat memory.
  • Multi-Agent Orchestration: Define orchestrator/worker/reviewer limits, concurrency rules, recovery protocols, and Claude Code subagent adapter rules for production-bound work.
  • Use Case: A team launching a new repository can run the bootstrap script and immediately have a complete, auditable engineering workflow that any future agent can follow without re-explanation.

Quick Start

Use the engineering-kernel skill to bootstrap or audit a repository's engineering workflow by applying the canonical project files and verifying kernel currency.

Frequently Asked Questions about engineering-kernel

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

FAQPage Schema
How do I bootstrap an agent-led engineering workflow in a new repository?

To bootstrap an agent-led engineering workflow, you materialize canonical project files like AGENTS.md, issue templates, and PRD-first policies into the repository. This provides a deterministic operating system that eliminates chat-memory dependence for future agents.

What is PRD-first execution and how does it work with GitHub issue decomposition?

PRD-first execution is a workflow canon that enforces building from product requirements before coding. It works with GitHub issue decomposition by breaking down PRDs into structured, machine-readable tasks that orchestrator and worker agents can process deterministically.

Can I use this engineering kernel for multi-agent orchestration with both GPT and Claude models?

Yes, the engineering kernel is model-agnostic and supports multi-agent orchestration across GPT/Codex and Claude-style agents. It defines orchestrator, worker, and reviewer limits alongside concurrency rules and Claude Code subagent adapter rules for production-bound work.

What's the best way to enforce workflow canon and verification discipline without relying on chat memory?

The best way to enforce workflow canon without chat memory is applying machine-readable policy YAML and project-local templates. This establishes deterministic verification discipline and bug intake rules that all current and future agents must follow.

How do I audit an existing repository for kernel drift and workflow policy compliance?

You audit a repository for kernel drift by running the bootstrap script's verification logic against existing project files. This detects missing AGENTS.md configurations, outdated templates, and unenforced engineering policies to ensure multi-agent coordination remains compliant.

Do I need specific dependencies to apply engineering workflow templates across different agents?

No external dependencies are required to apply the engineering workflow templates. The kernel provides self-contained bootstrap scripts and materialized project-local files, ensuring any repository can enforce multi-agent release coordination immediately without extra package installations.