Archon
Purpose
Manage Archon tasks in a project: list with filters, create with required fields, update by taskId, and use status values todo, doing, review, done exactly—coordinating with jira when the user wants cross-system sync.
When to Use
- List or search tasks by
projectId, status, or q.
- Create tasks with title (and optional description/status).
- Update task fields or status.
- Check Archon service health.
When NOT to Use
- Jira-only workflows without Archon → jira.
- Generic project planning → maintain-project-plan when that fits better.
Expected Outcome
- Task lists with id, title, status, projectId from
archon_list_tasks.
- Creates/updates confirmed from API responses.
- Jira changes only via jira when user asked to sync both systems.
Inputs to Gather
projectId for list/create.taskId for updates.- Status one of:
todo, doing, review, done.
Workflow
- List first when scope is unclear:
archon_list_tasks (projectId, status, q, pagination).
- Create:
archon_create_task with projectId, title, optional description, status.
- Update:
archon_update_task with taskId and changed fields.
- Health (optional):
archon_health.
- For Jira alignment, use jira with MCP schemas after Archon changes or in parallel per user request.
Domain rules
- List before create/update when task set is unknown.
- Status values exactly: todo, doing, review, done.
- Sync with Jira only when explicitly requested—use both tool sets.
Main tools
archon_list_tasks (projectId, status, q, includeClosed, page, perPage)archon_create_task, archon_update_task, archon_health
Examples
In-progress tasks: archon_list_tasks with status: "doing".
Create Review PR: archon_create_task with projectId, title, status: "todo".
Tool Availability Rules
| Access |
Behavior |
| Full tool access |
List, create, update. |
| Read-only |
List/get only. |
| No integration |
Do not fabricate task ids. |
Related tool sets
Review / Decision / Execution Criteria
- Keep status vocabulary strict.
- Cross-system sync: report Archon and Jira outcomes separately.
Output Format
- Project/task scope.
- Task table or mutation confirmation.
- Errors.
- Jira follow-up if sync requested.
Quality Bar
- IDs from tool output only.
- Pagination for large boards.
Safety and Boundaries
- Confirm bulk status changes.
Escalation / Dispatch Rules
- Jira-only → jira.
- Missing projectId → ask user before create.
References
- Legacy:
skills/old_skills.json (archon).
skills/skill.instruction.md, skills/meta.instructions.md
1---2name: archon3description: Lists, creates, and updates Archon tasks with statuses todo, doing, review, and done via archon_* tools. Use for Archon workboards and optional alignment with Jira.4---56# Archon78## Purpose910Manage Archon tasks in a project: list with filters, create with required fields, update by `taskId`, and use status values `todo`, `doing`, `review`, `done` exactly—coordinating with **jira** when the user wants cross-system sync.1112## When to Use1314- List or search tasks by `projectId`, `status`, or `q`.15- Create tasks with title (and optional description/status).16- Update task fields or status.17- Check Archon service health.1819## When NOT to Use2021- Jira-only workflows without Archon → **jira**.22- Generic project planning → **maintain-project-plan** when that fits better.2324## Expected Outcome2526- Task lists with id, title, status, projectId from `archon_list_tasks`.27- Creates/updates confirmed from API responses.28- Jira changes only via **jira** when user asked to sync both systems.2930## Inputs to Gather3132- `projectId` for list/create.33- `taskId` for updates.34- Status one of: `todo`, `doing`, `review`, `done`.3536## Workflow37381. **List first** when scope is unclear: `archon_list_tasks` (`projectId`, `status`, `q`, pagination).392. **Create**: `archon_create_task` with `projectId`, `title`, optional `description`, `status`.403. **Update**: `archon_update_task` with `taskId` and changed fields.414. **Health** (optional): `archon_health`.425. For Jira alignment, use **jira** with MCP schemas after Archon changes or in parallel per user request.4344### Domain rules45461. **List before create/update** when task set is unknown.472. **Status values** exactly: todo, doing, review, done.483. **Sync with Jira** only when explicitly requested—use both tool sets.4950### Main tools5152- `archon_list_tasks` (`projectId`, `status`, `q`, `includeClosed`, `page`, `perPage`)53- `archon_create_task`, `archon_update_task`, `archon_health`5455### Examples5657**In-progress tasks:** `archon_list_tasks` with `status: "doing"`.5859**Create Review PR:** `archon_create_task` with `projectId`, `title`, `status: "todo"`.6061## Tool Availability Rules6263| Access | Behavior |64|--------|----------|65| Full tool access | List, create, update. |66| Read-only | List/get only. |67| No integration | Do not fabricate task ids. |6869### Related tool sets7071- `task-manager`7273## Review / Decision / Execution Criteria7475- Keep status vocabulary strict.76- Cross-system sync: report Archon and Jira outcomes separately.7778## Output Format79801. Project/task scope.812. Task table or mutation confirmation.823. Errors.834. Jira follow-up if sync requested.8485## Quality Bar8687- IDs from tool output only.88- Pagination for large boards.8990## Safety and Boundaries9192- Confirm bulk status changes.9394## Escalation / Dispatch Rules9596- Jira-only → **jira**.97- Missing projectId → ask user before create.9899## References100101- Legacy: `skills/old_skills.json` (`archon`).102- `skills/skill.instruction.md`, `skills/meta.instructions.md`
poly-gents