@rasensio/aidlc-content 1.50.0 → 1.52.0

package/skills/00-overview.md

@@ -28,7 +28,7 @@ The AIDLC defines seven ordered phases. Not all apply to every task:
 1. **Ideation** — Problem exploration, goals, constraints
 2. **Requirements** — Acceptance criteria, user stories, scope
 3. **Design** — Architecture, interfaces, data flow
-4. **Implementation** — Code production following the design
+4. **Implementation** — Code following the design; agent per task: `.aidlc/resources/rules/task-agents.md`
 5. **Testing** — Verification against requirements
 6. **Deployment** — Release preparation and execution
 7. **Maintenance** — Monitoring, iteration, documentation updates
@@ -36,7 +36,7 @@ The AIDLC defines seven ordered phases. Not all apply to every task:
 ## Cycle Scopes
 
 | Scope | Starting Phase | Applicable Phases |
-|-------|---------------|-------------------|
+|---|---|---|
 | Full | Ideation | All seven phases |
 | Standard | Requirements | Requirements through Deployment |
 | Micro | Implementation | Implementation and Testing only |
@@ -133,7 +133,7 @@ An instance's **completion moment** is when the last applicable phase (template
 
 - Project context lives in `.aidlc/context/` (style-guide.md, architecture.md)
 - Guidance layers live in `.aidlc/guidance/` — load only those listed in `index.yaml`
-- Load context relevant to the current phase; avoid re-reading unchanged files
+- Why AIDLC works as it does: `aidlc explain` lists topics, `aidlc explain <topic>` prints one
 
 ### The always-read rule
 

package/skills/30-design.md

@@ -58,10 +58,13 @@ transcript. See **The context rule** (`.aidlc/resources/rules/context.md`).
    - [ ] T<n>: <title> (AC-1, AC-2)
    - [x] T<n>: <title> (AC-3)
    - [>] T<n>: <title> (AC-4) (deferred YYYY-MM-DD: <reason>)
+   - [ ] T<n>: <title> (AC-5) (wave: 2)
    ```
 
    Number tasks sequentially (`T1`, `T2`, ...) — IDs are never renumbered or reused; a task overtaken by events is deferred with a reason, never deleted. Reference the acceptance criteria each task satisfies where any apply; chore or infrastructure tasks may legitimately have none (the implementation gate surfaces them as warnings, never failures).
 
+   **Mark tasks that can run at the same time with `(wave: <n>)`**, `<n>` a whole number from 1. Tasks sharing a wave may be handed to separate agents at once, so give two tasks the same wave only when they touch different files and neither needs the other's output. A wave is a run of consecutive tasks — T4, T5 and T6, never T4 and T6 with T5 between them; the parser warns on a split wave. A task with no wave runs alone, in number order. Leave waves out when nothing can run alongside anything else: they matter only when implementation runs one agent per task.
+
 ## Exit Criteria
 
 - `design.md` exists with architecture, interfaces, and at least one design decision with rationale

package/skills/40-implementation.md

@@ -28,6 +28,7 @@ Read only:
 - `requirements.md` — the acceptance criteria the next task claims
 - the always-read guidance layers named in `.aidlc/guidance/index.yaml` (see **The always-read rule** (`.aidlc/resources/rules/always-read.md`))
 - `.aidlc/context/style-guide.md`
+- `implementation-questions.md`, when it exists — whether tasks go to one agent each
 
 Then the source files that task touches. See **The context rule** (`.aidlc/resources/rules/context.md`).
 
@@ -44,6 +45,8 @@ Then the source files that task touches. See **The context rule** (`.aidlc/resou
 2. **Load guidance.** Read the always-read guidance layers from `.aidlc/guidance/index.yaml` — see **The always-read rule** (`.aidlc/resources/rules/always-read.md`) for which layers those are and when to reach for the full `lessons.md`. Apply their rules during implementation.
 3. **Check that the planning artifacts agree.** Before the first task, run `aidlc cross-check <instance>` and show the user the list. It reads `requirements.md`, `design.md` and `tasks.md` side by side and prints one line per gap — a criterion no task cites, a task citing no criterion, a criterion design never mentions — each naming both artifacts and the ID. It is a report: it writes nothing and never blocks, and acting on a gap is the user's call. A gap in `tasks.md` is fixed in place, since its phase is still open here; a gap in a completed `requirements.md` or `design.md` is fixed through an amendment (**Amending a Completed Phase**, in the requirements skill), never by editing it silently. Unattended (`AIDLC_UNATTENDED=1`): record the list in `code-complete.md` and carry on.
 4. **Execute the task breakdown.** When the instance has a `tasks.md` (produced in Design for full/quick-feature scope), read it and execute tasks in order: complete a task, then mark its checkbox `[x]` as part of the same work unit — never batch checkbox updates for later. A task that should not be done is deferred in place (`- [>] T<n>: <title> (deferred YYYY-MM-DD: <reason>)`) with a dated reason, never skipped silently or deleted; the implementation→testing gate blocks on open tasks. For bugfix scope, create the optional `tasks.md` at implementation start when the fix spans more than one commit-sized unit. For Micro scope, reference the task description and acceptance criteria directly — no task file.
+
+   **One agent per task.** Where the platform's entry for this skill says sub-agents are available and the instance has a task-bearing `tasks.md`, offer it before the first task — or follow the answer already recorded in `implementation-questions.md` — exactly as **The task-agents rule** (`.aidlc/resources/rules/task-agents.md`) says. Chosen, it replaces the task-by-task work above: each task goes to a fresh agent, a second agent reviews it, and the box is ticked only after that review passes. Not offered, or not chosen, run every task in this session as before.
 5. **Write code.** Follow the design interfaces. Match existing code style (naming, formatting, error handling patterns).
 6. **Handle sensitive operations.** Before executing any of the following, describe the action and wait for explicit user confirmation (unattended, `AIDLC_UNATTENDED=1`: each is a hard stop except reverting this session's own changes, per `.aidlc/resources/rules/unattended.md`):
    - File deletions or destructive operations