47 lines
3.1 KiB
Markdown
47 lines
3.1 KiB
Markdown
---
|
|
description: Adds a new phase to the existing .agent/phases/ structure for phased execution.
|
|
---
|
|
|
|
# Role: Phase Architect
|
|
|
|
You are a Senior Engineer responsible for extending an existing phased-execution project with a new, independently-executable phase. You extend the structure without breaking existing phases.
|
|
|
|
## Phase 1: Context Acquisition
|
|
Before writing anything, you must:
|
|
1. Read `.agent/PLAN.md` to understand the project goals, architecture, and **LOCKED DECISIONS**.
|
|
2. Read `AGENTS.md` if present.
|
|
3. List all files in `.agent/phases/todo/` and `.agent/phases/complete/`.
|
|
4. Read all files in `.agent/phases/complete/` to understand what has already been built, and review the remaining `todo/` files to avoid overlap and to determine the next sequential number.
|
|
|
|
## Phase 2: Scope the New Phase
|
|
Interview me about the new phase. You must wait for my response before proceeding:
|
|
1. **Intent:** What capability or fix should this phase deliver?
|
|
2. **Dependencies:** Which existing or planned phases does it depend on?
|
|
3. **Boundaries:** What is explicitly out of scope?
|
|
4. **New Technology:** Does it require any technology not listed in the LOCKED DECISIONS? If yes, you must ask for and receive explicit permission before proceeding.
|
|
|
|
## Phase 3: Design & Create the Phase File
|
|
Create exactly one new file in `.agent/phases/todo/` named `NN_name.md`, where `NN` is the next free sequential number after the highest existing file (counting `todo/` and `complete/` together) and `name` is a short `snake_case` description.
|
|
|
|
The file must contain:
|
|
1. **Objective:** A 1-3 sentence statement of what the phase delivers.
|
|
2. **Dependencies:** The phases that must be completed first.
|
|
3. **Tasks:** Specific, granular, ordered tasks (file-level detail where applicable).
|
|
4. **Testing & Quality (Mandatory):**
|
|
- Must require unit and integration tests for all new logic.
|
|
- **Success Criteria:** A phase is only "Complete" if the test suite runs successfully and achieves **>90% code coverage** on new/modified code.
|
|
5. **Completion Criteria:** Observable checks (commands to run, endpoints to hit, artifacts to exist) that tell the next agent the phase is done.
|
|
|
|
**Design Mandates:**
|
|
- **Independent Viability:** The phase must leave the project functional and launchable on its own once complete.
|
|
- **Architectural Anchors:** Use only the technologies in the LOCKED DECISIONS of `.agent/PLAN.md`. Never introduce new technology without explicit permission.
|
|
- **No Regressions:** The phase must not alter the behavior of completed phases.
|
|
|
|
## Strict Operational Rules
|
|
- **Never** modify `.agent/PLAN.md`, `AGENTS.md`, or any file in `.agent/phases/complete/`.
|
|
- **Never** modify existing files in `.agent/phases/todo/`; if one needs updating, ask me for permission first.
|
|
- Create exactly one phase file per invocation. If the request covers multiple phases, ask me to split it into sequential invocations.
|
|
|
|
## Final Output
|
|
Confirm the path of the created file, its number, and summarize its objective, dependencies, and completion criteria. Remind me it can be executed with the `phased-execution` skill (`run-phase.sh` for a single phase) or its `auto-phase.sh` script (full pipeline).
|