# Alexnodeland Principled New Plan

> New Plan — DDD Implementation Plan Creation

- Skill: `tomevault-io/alexnodeland-principled-new-plan` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/alexnodeland-principled-new-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/alexnodeland-principled-new-plan/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/alexnodeland-principled-new-plan

---


# New Plan — DDD Implementation Plan Creation

Create a domain-driven implementation plan that implements an accepted proposal, informed by its related ADRs.

## Command

```
/new-plan <short-title> --from-proposal NNN [--module <path>] [--root]
```

## Arguments

| Argument              | Required | Description                                                                       |
| --------------------- | -------- | --------------------------------------------------------------------------------- |
| `<short-title>`       | Yes      | Short, hyphenated title for the plan                                              |
| `--from-proposal NNN` | **Yes**  | The number of the originating proposal. The proposal must have status `accepted`. |
| `--module <path>`     | No       | Target module path                                                                |
| `--root`              | No       | Create at repo root level                                                         |

## Workflow

1. **Parse arguments.** Extract title and `--from-proposal NNN` from `$ARGUMENTS`. The `--from-proposal` flag is required — plans always originate from an accepted proposal.

2. **Locate and verify the proposal.** Find the proposal matching NNN in the appropriate `docs/proposals/` directory. Read its frontmatter and verify:
   - The proposal exists
   - Its `status` is `accepted`
   - If not accepted, report an error: _"Cannot create plan: proposal NNN has status '\<status\>'. Only accepted proposals can have implementation plans."_

3. **Discover related ADRs.** Scan the `docs/decisions/` directory for ADRs whose `originating_proposal` field matches NNN. These are the decisions that inform this plan.

4. **Get next sequence number.** Run:

   ```bash
   bash scripts/next-number.sh --dir <target-plans-dir>
   ```

5. **Read DDD guidance.** Before creating the plan, read `reference/ddd-guide.md` to inform the decomposition approach. Use this guidance to help the user structure their bounded contexts, aggregates, and domain events.

6. **Create the plan file.** Read the template from `templates/plan.md` and create `<target>/NNN-<short-title>.md`.

7. **Populate frontmatter:**

   | Field                  | Value                                      |
   | ---------------------- | ------------------------------------------ |
   | `title`                | Derived from the short title               |
   | `number`               | The NNN from step 4                        |
   | `status`               | `active`                                   |
   | `author`               | Git user name or prompt                    |
   | `created`              | Today's date                               |
   | `updated`              | Today's date                               |
   | `originating_proposal` | The proposal number from `--from-proposal` |
   | `related_adrs`         | Array of ADR numbers discovered in step 3  |

8. **Pre-populate from proposal and ADRs.** Read the originating proposal's content and related ADRs to seed:
   - The Objective section (link to proposal)
   - Related Decisions section (links to all discovered ADRs)
   - Initial bounded contexts (derived from proposal scope and ADR decisions)
   - Known dependencies

9. **Confirm creation.** Report the created file and guide the user to:
   - Complete the domain analysis (bounded contexts, aggregates, domain events)
   - Define implementation tasks per the DDD guide

## Plan Lifecycle

| State       | Description                                               |
| ----------- | --------------------------------------------------------- |
| `active`    | Work is in progress. Plan is mutable.                     |
| `complete`  | All tasks are done.                                       |
| `abandoned` | Plan was abandoned. Originating proposal may still stand. |

## Reference

- `reference/ddd-guide.md` — Practical guide to DDD decomposition for implementation plans

## Templates

- `templates/plan.md` — DDD implementation plan template (copy of `scaffold/templates/core/plan.md`)

## Scripts

- `scripts/next-number.sh` — Determines the next NNN sequence number

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/alexnodeland) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->