axiomantic
Official@axiomantic
Offers structured engineering governance, test-driven development, and multi-agent coordination for complex software lifecycle management and quality assurance.
Agent Skills by axiomantic
Showing 49 vetted skills indexed across 2 GitHub repositories.
axiomanticAdding Plugins to tripwire
Guide developers through adding Tripwire plugins from discovery to documentation.
axiomanticspellbook-auditing
Audit Spellbook skills, commands, and documentation for quality and consistency.
axiomanticdocumentation-updates
Sync CHANGELOG, README, and docs after library changes.
axiomanticassembling-context
Assemble tiered context packages within token budgets for multi-agent workflows.
axiomanticusing-git-worktrees
Manage separate project builds for the same or different target frameworks, and optionally the same for different CPU architectures.
axiomanticautonomous-roundtable
Coordinate staged autonomous project development across DISCOVER, DESIGN, PLAN, IMPLEMENT, and COMPLETE phases with subagents and roundtables.
axiomanticasync-await-patterns
Enforce async/await for JavaScript and TypeScript asynchronous code.
axiomantictest-driven-development
Enforce a red-green-refactor workflow by writing failing tests before production code.
axiomanticfact-checking
Identify and triage verifiable claims in code and documentation with evidence.
axiomanticdevils-advocate
Identify flaws and surface risks in design documents and decisions.
axiomanticfinding-dead-code
Identify dead code with caller evidence and removal plans.
axiomanticusing-lsp-tools
Provides semantic navigation and accurate extraction of text, tables, and metadata from PDF files.
axiomanticreflexion
Parse ITERATE feedback, extract root causes, and store reflections in forge.db.
axiomanticreviewing-design-docs
Identify gaps and ambiguities in design documents before implementation.
axiomanticanalyzing-skill-usage
Analyze session transcripts to extract invocation patterns and per-skill scores.
axiomanticdispatching-parallel-agents
Decide when to dispatch subagents versus stay in the main context.
axiomanticmanaging-artifacts
Organize generated artifacts into a centralized directory under ~/.local/spellbook.
axiomanticsmart-reading
Measure unknown file or command output size before reading or delegating to subagents.
axiomanticcode-review
Route code reviews to mode-specific handlers and generate findings with severity and file:line references.
axiomanticdebugging
Guides debugging workflows from triage to verification with structured decision points.
axiomanticdesigning-workflows
Formalize business processes into state machines with mermaid diagrams and transition tables.
axiomanticfun-mode
Configure a Creative Dialogue Director persona with context and undertow for bounded conversations.
axiomanticexecuting-plans
Executes written implementation plans step-by-step with mandatory verification evidence.
axiomanticfinishing-a-development-branch
Enforce test success before merging, PR creation, or discarding feature branches.
Frequently Asked Questions About axiomantic
FAQPage SchemaWhat specific engineering tasks are enabled by these capabilities?▼
These capabilities enable rigorous test-driven development, automated code review routing, structured design document auditing, and the formalization of business processes into state machines. It facilitates end-to-end feature implementation, artifact management, and the systematic identification of dead code or coverage gaps.
Which personas benefit most from these engineering practices?▼
Senior software engineers, technical leads, and quality assurance architects benefit from these practices. The framework is designed for developers managing complex, multi-branch projects who require strict adherence to quality standards, traceable decision logs, and structured peer-review processes.
What are the prerequisites for integrating these practices into a project?▼
Integration requires a Git-based version control environment and a commitment to test-driven development standards. Users should maintain a structured project directory, typically utilizing the ~/.local/spellbook path for artifact persistence, and ensure their codebase supports modular, phase-gated development cycles.