factory-droid-audit

Name: factory-droid-audit
Availability: InStock
Author: Ludwig

Verify Factory Droid mission progress against mission specifications and git history.

Updated Apr 8, 2026

Search Tags:#drift detection #verification #audit #acceptance criteria #git history #mission progress

Ready to run

npx skills add https://github.com/LudwigAJ/swell --skill factory-droid-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: factory-droid-audit
Source: https://github.com/LudwigAJ/swell/tree/main/.claude/skills/factory-droid-audit
Command: npx skills add https://github.com/LudwigAJ/swell --skill factory-droid-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you confirm whether Factory Droid actually completed the work it claimed, instead of relying on self-reported status or partial automation output.

Core Features & Use Cases

Mission Verification: Cross-check reported feature completion against mission files, git history, and validation artifacts.
Acceptance Audit: Run the specified grep, test, and build checks to confirm that milestone criteria are truly met.
Drift Detection: Catch common failure modes such as missing commits, incomplete migrations, unused imports, and test-only features leaking into production.
Use Case: Before approving a milestone, use this Skill to produce an evidence-based audit that separates verified completion from in-progress or misreported work.

Quick Start

Ask the factory-droid-audit skill to verify a Droid mission milestone against the mission spec, git history, and acceptance criteria.

Frequently Asked Questions about factory-droid-audit

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

FAQPage Schema

How do I verify automated coding mission progress against acceptance criteria?▼

Verify automated coding mission progress by cross-referencing mission files, running spec-driven grep and test commands, and checking git history to validate that acceptance criteria are truly met.

What is drift detection in automated feature completion?▼

Drift detection in automated feature completion identifies common failure modes such as missing commits, incomplete migrations, unused imports, and test-only features leaking into production code.

How do I audit git history for milestone completion claims?▼

Audit git history for milestone completion claims by cross-checking reported feature completion against mission files, git logs, and validation artifacts to separate verified completion from misreported work.

Can I use spec-driven grep checks to validate swarm-delivered coding milestones?▼

Yes, you can validate swarm-delivered coding milestones by running specified spec-driven grep, test, and build checks to confirm that milestone acceptance criteria are genuinely fulfilled.

Why does my automated mission report show incomplete migrations or unused imports?▼

Automated mission reports show incomplete migrations or unused imports due to code drift patterns, where the delivered output diverges from the mission specification and requires an evidence-based audit to catch.

What is the best way to confirm Factory Droid milestone completion before approving?▼

The best way to confirm Factory Droid milestone completion is producing an evidence-based audit that cross-references mission files, runs validation checks, and detects drift patterns instead of relying on self-reported status.