agentic-workflow / references
AGENTS.md4 starsChanged 29 days agoMITView on GitHub
Loaded by dev-methodology when an agent needs to identify which sibling agent to dispatch for a sub-task. Hot-path summary lives in dev-methodology/SKILL.md §"Agents" — it points here for the full per-role catalog. Agents are isolated subprocesses with fresh context. They receive input, do one job, return structured output.
In this repository48 other files it gives its agents.
- skills/skill-authoring/references/agents.mdAGENTS.md
- acceptance-protocolSkill
- agency-intakeSkill
- ai-visibility-methodologySkill
- banner-design-guideSkill
- benchmark-researchSkill
- brand-methodologySkill
- code-reviewingSkill
- code-writingSkill
- codex-bridgeSkill
- deploy-pipelineSkill
- design-assets-guideSkill
- design-system-methodologySkill
- design-task-decompositionSkill
- dev-methodologySkill
- docs-pipelineSkill
- documentation-writingSkill
- engagement-contractSkill
- engagement-protocolSkill
- feature-researchSkill
- human-voiceSkill
- infrastructure-setupSkill
- marketing-task-decompositionSkill
- post-deploy-qaSkill
- pre-deploy-qaSkill
- presentation-designSkill
- project-planningSkill
- prompt-engineeringSkill
- security-auditingSkill
- semantic-drift-methodologySkill
- seo-auditingSkill
- skill-authoringSkill
- skill-test-designSkill
- skill-testingSkill
- system-optimization-protocolSkill
- task-decompositionSkill
- tech-spec-planningSkill
- testing-methodologySkill
- ui-styling-guideSkill
- ui-ux-methodologySkill
- user-spec-planningSkill
- validation-pipelineSkill
- yandex-analytics-methodologySkill
- yandex-direct-guideSkill
- yandex-metrika-guideSkill
- yandex-search-guideSkill
- yandex-webmaster-guideSkill
- yandex-wordstat-guideSkill
The file
Files
Dev Agents — full catalog
Loaded by dev-methodology when an agent needs to identify which
sibling agent to dispatch for a sub-task. Hot-path summary lives in
dev-methodology/SKILL.md §"Agents" — it points here for the full
per-role catalog.
Agents are isolated subprocesses with fresh context. They receive input, do one job, return structured output.
Dev Track Leadership
dev-director— system-optimizer (out-of-band); does NOT accept engagementsdev-manager— acceptor for dev-lead handoffs; writes accept/reject verdict (does not plan or execute)dev-lead— plans the engagement (thelead:planstep of theengagement-workflowWorkflow); does NOT dispatch — the Workflow script fans out specialists/validatorsdev-tech-architect— tech-spec author + task decomposition
Validators (run during spec/task creation)
userspec-quality-validator— document quality and completenessuserspec-adequacy-validator— solution feasibilityinterview-completeness-checker— interview coverage gapstech-spec-validator— template complianceskeptic— detects mirages (non-existent files/functions/APIs)completeness-validator— bidirectional requirements traceability, over/underengineering, solution depthtask-validator— task template compliancetask-creator— generates task files from tech-specreality-checker— validates tasks against codebasefeasibility-assessor— validates feature research verdict (scope, risks, justification)
Reviewers (run during/after code writing)
code-reviewer— code quality across 10 dimensionstest-reviewer— test quality analysis with concrete fixessecurity-auditor— OWASP Top 10, auth, input validationperformance-validator— N+1 queries, memory leaks, O(n²), async anti-patternsmigration-validator— DB migration safety: atomicity, rollback, data preservationaccessibility-validator— WCAG AA: ARIA, contrast, keyboard nav, screen readersprompt-reviewer— prompt quality against prompt-engineering principlesdocumentation-reviewer— project-knowledge quality (haiku model — template check)deploy-reviewer— CI/CD pipeline and deployment configuration (haiku model)infrastructure-reviewer— folder structure, Docker, pre-commit hooks, .gitignore (haiku model)
Engineers (implementation)
dev-backend-engineer— server-side (APIs, services, DB, background jobs)dev-frontend-engineer— client-side (UI components, state, routing)dev-fullstack-engineer— end-to-end features when split adds no valuedev-devops-engineer— infrastructure + CI/CDdev-technical-writer— project-knowledge maintenancedev-qa-engineer— test strategy + plans
Research
code-researcher— codebase research for features (files, patterns, tests, integrations, risks)
QA
pre-deploy-qa— pre-deploy acceptance testing (tests + acceptance criteria)post-deploy-qa— post-deploy verification on live environment (MCP tools, AVP)
Meta
skill-checker— validates skills against skill-authoring standards
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

