How do I install the Alexnodeland Principled New Plan skill?

Run npx skillmds@latest add tomevault-io/alexnodeland-principled-new-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Alexnodeland Principled New Plan skill do?

New Plan — DDD Implementation Plan Creation It is listed under Coding & Dev Tools on SkillMD.

Is Alexnodeland Principled New Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Alexnodeland Principled New Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Alexnodeland Principled New Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Alexnodeland Principled New Plan?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Alexnodeland Principled New Plan by tomevault-io

Name: Alexnodeland Principled New Plan
Author: tomevault-io

File contents

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

Parse arguments. Extract title and --from-proposal NNN from $ARGUMENTS. The --from-proposal flag is required — plans always originate from an accepted proposal.
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."
Discover related ADRs. Scan the docs/decisions/ directory for ADRs whose originating_proposal field matches NNN. These are the decisions that inform this plan.

Get next sequence number. Run:

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

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.
Create the plan file. Read the template from templates/plan.md and create <target>/NNN-<short-title>.md.

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

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
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 — claim your Tome and manage your conversions.

---name: alexnodeland-principled-new-plandescription: New Plan — DDD Implementation Plan Creation---# New Plan — DDD Implementation Plan CreationCreate 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 |## Workflow1. **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 dependencies9. **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.

Frequently asked questions

Alexnodeland Principled New Plan