neckbeard

Route software changes through framing, discovery, design, implementation, and verification stages.

40|6|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/magnus919/agent-skills --skill neckbeard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neckbeard
Source: https://github.com/magnus919/agent-skills/tree/main/bundles/neckbeard
Command: npx skills add https://github.com/magnus919/agent-skills --skill neckbeard

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of unreliable, "persona-based" AI software development by enforcing a rigorous, evidence-based workflow that prioritizes verifiable outcomes over confident but unproven code.

Core Features & Use Cases

  • Evidence-Led Delivery: Ensures every change is framed, discovered, and verified at the real delivery boundary, preventing "10x developer" shortcuts.
  • Specialist Composition: Acts as an orchestrator that routes specific tasks (like debugging, security, or architecture) to the appropriate specialist skills while maintaining a unified evidence ledger.
  • Use Case: When tasked with a non-trivial feature or bug fix, use this skill to generate a change contract, perform systematic discovery, and produce an audit-ready evidence ledger that proves the change works at the production boundary.

Quick Start

Load the neckbeard skill and follow its core loop to frame your software change contract and begin the evidence-driven delivery process.

Frequently Asked Questions about neckbeard

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

FAQPage Schema
How do I enforce an evidence-driven software delivery workflow for complex feature development?

An evidence-driven workflow prevents unreliable AI development by generating a change contract, performing systematic discovery, and maintaining an audit-ready evidence ledger. This skill enforces that discipline by routing tasks through five stages to verify outcomes at the production boundary.

What is an evidence ledger in software engineering and when do I need one?

An evidence ledger is an inspectable record proving a software change works at the production delivery boundary. You need one during non-trivial engineering tasks like bug diagnosis or refactoring to ensure verifiable outcomes over confident but unproven code.

How do I stop AI agents from taking 10x developer shortcuts when fixing bugs in complex systems?

To stop AI shortcuts during bug diagnosis, route tasks through a disciplined operating model requiring framing, systematic discovery, and verification. This skill enforces an evidence-based workflow prioritizing verifiable outcomes over unproven code.

Do I need a specific agent harness to use an evidence-led software delivery discipline?

Yes, evidence-led delivery requires an agent harness capable of file operations, terminal access, and dynamic skill loading. These capabilities maintain the inspectable evidence ledger throughout the software engineering lifecycle.

Can I use this workflow for refactoring within complex systems?

Yes, this workflow applies to refactoring within complex systems alongside bug diagnosis and feature development. It routes non-trivial software engineering tasks through a rigorous evidence-based process verifying changes at the real delivery boundary.

How does specialist composition work for software engineering tasks like debugging or architecture?

Specialist composition works by orchestrating specific tasks like debugging, security, or architecture to appropriate specialist skills. It maintains a unified evidence ledger across all routed tasks ensuring consistent verification.