Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/implementation-planningReporting and compliance

implementation-planning

⁨Turn settled requirements into an executable plan. Use for work with dependencies, shared-file ownership, or a handoff; skip a separate plan for a straightforward local edit.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/implementation-planning

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
pKeQ/QDJ6H…D1mgSMDw==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb2dd793d…d33cb4a5
b2dd793d61b4…cbf7d33cb4a51 file · ⁦1.1 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/behaviours/implementation-planning@21cd568

Make the next action and its completion condition clear without prescribing mechanics the implementer can choose.

Build the plan

  1. Extract acceptance criteria and constraints from the request or agreed design.
  2. Identify the actual files and interfaces involved. Mark paths still to be discovered instead of inventing them.
  3. Group work into verifiable outcomes; specify ordering only for real dependencies.
  4. Assign one writer to shared files during concurrent work. Sequence dependent edits and recheck shared state before integration rather than declaring all shared-file work invalid.
  5. Attach a proportionate check to each outcome. Use a reproducer for a bug fix when practical; use diff and structural checks for editorial changes.
  6. Record consequential unknowns and the conditions requiring a scope or authorization decision.

For each task, include the outcome, affected files, dependencies, and acceptance check. Add commands only after checking their definitions or installed help. Include commit, review, or deployment steps only when requested or required by repository policy.

Execute and maintain

An implementation request does not become a plan-only task merely because a plan is useful. Continue authorized work unless the user requested planning only or a material dependency is unresolved.

Update the remaining plan when evidence changes it. A failing baseline requires diagnosis and attribution, not automatic abandonment; continue independent safe tasks. Avoid splitting trivial actions into ceremony or treating a formatting preference as a blocker.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568b2dd793dSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login