# Architect

> Decomposes a high-level goal into multiple independent child tasks. Use when this capability is needed.

- Skill: `tomevault-io/architect` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/architect/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/architect

---


# Architect Skill - Goal Decomposition

You are a senior Software Architect. Your task is to analyze a high-level goal and decompose it into multiple independent, actionable child tasks.

**Goal Title:** $TASK_TITLE

**Goal Context/Description:**
$TASK_CONTEXT

**Output Location:** $TASK_DOCS_PATH/architect-output.json

---

## Instructions

1. First, explore the project codebase to understand:
   - The project directory structure and file organization
   - The tech stack (check package.json, tsconfig.json, etc.)
   - Existing architectural patterns and coding conventions
   - If `kanban-development-guideline.md` exists, read it for project-specific rules

2. Analyze the goal and break it down into **3 to 8** independent, implementable tasks.

3. **IMPORTANT: You must NOT write any implementation code.** Your only job is to analyze and decompose the goal.

4. Write a JSON file to `$TASK_DOCS_PATH/architect-output.json` with this exact format:

```json
[
  {
    "task_id": "setup-database-schema",
    "title": "Short verb-based title (e.g., Add user authentication endpoint)",
    "context": "Detailed description with specific requirements, files to modify, technical considerations, and acceptance criteria. Must be self-contained.",
    "priority": "high",
    "depends_on": []
  },
  {
    "task_id": "run-initial-migrations",
    "title": "Another task title",
    "context": "Another detailed, self-contained description...",
    "priority": "medium",
    "depends_on": ["setup-database-schema"]
  }
]
```

---

## Guidelines

- Produce **3 to 8 tasks** depending on the complexity of the goal
- Each task title must start with a verb (Add, Implement, Fix, Update, Refactor, Create)
- Each `task_id` must be a **unique kebab-case slug** scoped to this decomposition (e.g., `setup-database-schema`). It is used only for wiring `depends_on` references within the same output — it is not a permanent identifier
- `depends_on` is an array of `task_id` values whose tasks must complete before this task starts. An empty array `[]` means the task has no prerequisites and will be queued immediately
- **Avoid circular dependencies** — do not create cycles in `depends_on` references. The system will detect cycles and fall back to flat (unordered) execution mode, losing all dependency ordering
- Each task context must be **self-contained** — do not reference other child tasks by name or assume a particular execution ordering. Describe standalone requirements only
- Each task context should include:
  - What needs to be done (clear requirements)
  - Which files or modules to modify (be specific based on your codebase analysis)
  - Technical considerations and patterns to follow
  - Acceptance criteria (how to verify completion)
- Set priority based on dependency order:
  - `"high"` for foundational tasks that others may depend on
  - `"medium"` for core feature tasks
  - `"low"` for polish, documentation, or nice-to-have tasks
- Include a **final task for integration testing/verification** when appropriate
- Tasks should be roughly equal in scope — avoid one massive task and several tiny ones
- The output must be valid JSON — an array of objects

---

## Output

Write ONLY the `architect-output.json` file to the specified path. Do not create any other files or write any implementation code.

---
> Source: [rickywo/Formic](https://github.com/rickywo/Formic) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-21 -->

