Practical, source-faithful workflows for AI-assisted software development.
MIT License · Quick start · Skills · Adaptation guide · Verification
Plan coherent changes. Refactor without losing behavior. Catch state and lifecycle bugs before completion. Preserve active workspaces when integrating branches.
This repository contains English adaptations of established workflows, their supporting references, and the original portable scripts and tests. Private infrastructure bindings are replaced with explicit project configuration. The workflows retain their detailed checks and decision rules.
Clone this repository:
git clone https://github.com/argon-analytik/reliable-agent-toolkit.git
cd reliable-agent-toolkitThen give your agent this request:
Read AI_HANDOFF.md. Inspect my target project read-only, recommend useful skills, and show an adaptation preview. Preserve my existing rules, language, and local changes.
The handoff helps adapt the toolkit to your environment. You do not need a Knowledge Base, coordination department, or hosted service to start.
For a manual installation preview:
python3 scripts/install.py --target ../my-project/.agents/skills --skill software-sanity-checkAdd --apply after reviewing the destination. Repeat --skill to select additional workflows. The installer protects unmanaged files and modified installations. Installation and updates →
| Skill | The problem it addresses | What the workflow delivers |
|---|---|---|
| Software sanity check | A green build hides broken state or error handling | State ownership, edge-case review, appropriate verification |
| Concept to plan | Chat decisions become vague or overengineered plans | Outcome-based packages, real dependencies, templates and original plan linter |
| Code refactoring | Structural cleanup accidentally changes behavior | Baseline, invariants, responsibility-based cuts, full completion review |
| Repository refactoring | Moving files breaks references or loses knowledge | Inventory, path mapping, archive contract, reference and metadata checks |
| Main consolidation | Branch cleanup discards unique work or active task directories | Content classification, integration, remote-SHA verification, protected workspace handling |
| Workspace health check | Local links and configuration silently drift | Bounded local inspection with explicit coverage limits |
| Content SEO | Pages miss user intent or compete with one another | Research, intent mapping, briefs, original content inventory and overlap checks |
| Technical SEO | Crawl and indexing signals contradict one another | Original static audit, sitemap/link/metadata checks, configuration validator, live-evidence guidance |
| Design hygiene | Page-level fixes create competing visual rules | Parent/child classification, component/object/motion inventory, rendered verification |
| macOS performance audit | UI work blocks the main thread or invalidates too broadly | Code diagnosis, targeted fixes when requested, comparable runtime evidence |
| Publication polish | Editing makes prose smoother but changes its claims | Source-faithful revision, writing/message standards, licensed diagnostic references |
| Knowledge routing | Historical notes become accidental current authority | Canonical topic maintenance, source-role separation, index checks |
| Consistency review | Projects repair shared rules inconsistently | Deduplicated findings, one owner, concrete consumer resume evidence |
Detailed use cases and example requests →
Illustrative scenario: request B returns before request A. A's late response overwrites the newer results. The sanity check traces state ownership and ordering, then calls for a guard and a behavior test that completes requests out of order.
The refactoring workflows establish public APIs, persisted formats, errors, and lifecycle behavior before splitting code. Repository cleanup uses a path map and an archive contract; it does not silently redesign application logic.
Main consolidation distinguishes integrated source from disposable working directories. Active, primary, modified, or unknown-owner workspaces remain protected. A retained directory can be a successful completion result.
Consistency review records the mismatch once, identifies one source owner, and provides affected projects with verified delivery and resume instructions. Routine local edits require no controller conversation.
- Skills only: Select workflows for your existing repository.
- Skills and knowledge: Reuse current documentation or adapt the Knowledge Base template.
- Shared coordination: Add the Consistency Department template for concrete cross-project dependencies.
The workspace health checker and manual templates are explicitly identified as community additions. They do not claim feature parity with the private infrastructure engine. Scheduling remains optional and has no enabled adapter.
The translation preserves detailed workflows and relevant resources. Adaptations remove private endpoints, absolute user paths, mandatory infrastructure services, and universal Swiss typography. English instructions do not force your project content into English.
See source fidelity and adaptation decisions and provenance, including the MIT attribution for publication-polish references.
L0 local reversible work and L1 reading need no extra Go within the requested scope. L2 production changes and L3 destructive changes require the applicable proposal and human authorization.
These are toolkit conventions, not a universal standard. The optional intent inspector hashes proposal content; it neither authenticates a person nor authorizes execution. Approval model →
Python 3.10+ is required; the original Git auditor also requires Git.
python3 scripts/validate_all.py
python3 -m unittest discover -s tests -v
sh skills/concept-to-plan/tests/run-tests.sh
python3 -m unittest discover -s skills/content-seo/tests -v
python3 -m unittest discover -s skills/technical-seo/tests -vMeasured verification and limitations · Compatibility · Troubleshooting
Bring a concrete workflow problem and a reproducible example. Preserve source fidelity and document any portability change. Shorter wording alone is not a reason to remove useful instructions.