Agents Inventory
Purpose: List the Swifter agents that exist today, what each one is for, and how to invoke them — the canonical reference for any agent mentioned elsewhere in the blueprint.
| Agent code | Role / proficiency | Status |
|---|---|---|
swifter-default | Autonomous triage — entry agent that routes a work item to the right specialised agent. Invoked via /swifter-default:start. | Shipping |
swifter-frontend-analyst | Frontend specification — translates work items, Figma, and existing docs into Application Specifications (data model, presentation model, logic). Does not write production code. | Shipping |
swifter-frontend-developer | Frontend implementation — generates UI component code, page code, and integration code from analyst-produced specs. | Shipping |
swifter-backend-analyst | Backend specification — generates scoped specifications for endpoints, data models, and business logic. | Shipping |
swifter-backend-developer | Backend implementation — implements endpoints from scoped specifications. | Shipping |
swifter-backend-architect | Backend architecture — generates architecture guidelines, coding conventions, refactoring plans. Not for implementation. | Shipping |
swifter-tester | Testing — generates test cases and test scripts; executes them via Playwright. Commands include generate-test-cases, generate-test-scripts, onboard-existing-tests. | New; ramp-up in progress |
swifter-business-analyst | Business-context formalism — commands establish-business-context-connectivity, onboard-business-requirement-definition. | Implemented but unused on engagements to date |
swifter-autonomous | Reserved / future autonomous-start agent. | Reserved |
Nine agent codes are known to the platform today. Of those, the seven shipping agents are the ones engagement teams should expect to use; swifter-business-analyst is implemented but has not been used in a production engagement yet, and swifter-autonomous is reserved for future use.
Invoking an agent
Commands are invoked from inside a work session's chat as:
/swifter-<agent-code>:<command-name>
For example, /swifter-frontend-analyst:define-component-spec or /swifter-default:start. Skills are not directly invokable. MCP servers are the only sanctioned path for mutating data-model, logic, and component-metadata artefacts; agents should not use raw file-write tools to touch those files.
Per-agent command catalogue (partial)
The catalogue below lists commands documented in the plugin definitions or observed in production engagement data. Each agent has additional commands that are not yet inventoried here; consult the plugin's commands/ folder for the complete list.
| Agent | Documented commands |
|---|---|
swifter-default | start (autonomous triage) |
swifter-frontend-analyst | define-component-spec, define-page-spec, sync-component-specs, import-component-specs, generate-acceptance-criteria, plus lower-level commands such as fetch-figma-data, match-figma-styles, generate-figma-html-css, onboard-component, work-on-component-data-model, work-on-component-logic |
swifter-frontend-developer | generate-component, generate-page, work-on-component-logic (re-invoked against an existing page is how FE↔BE integration is wired — there is no dedicated integrate-api command) |
swifter-backend-analyst | generate-scoped-specifications |
swifter-backend-developer | implement-scoped-changes |
swifter-backend-architect | create-guidelines |
swifter-tester | generate-test-cases, generate-test-scripts, aem-generate-publish-cases, onboard-existing-tests |
swifter-business-analyst | establish-business-context-connectivity, onboard-business-requirement-definition |
The most-invoked single command observed in production engagement data is import-component-specs on the frontend analyst — the workhorse for sync and onboarding work items.