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/design-before-implementationReporting and compliance

design-before-implementation

⁨Clarify and review designs before substantial changes. Use when requirements, interfaces, alternatives, or success criteria are unclear; skip a separate design phase for an already specified local fix.⁩

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/design-before-implementation

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

SignatureSigned, ed25519
+11Y3GWWCc…J44xMsCA==The CLI checks the SHA-256 and the signature before it writes a file.
Package73ba773d…3126f801
73ba773d882a…7fde3126f8012 files · ⁦2.5 KB⁩
ScanMedium2 findings
  • injection.no_confirmationreferences/design-gates.md:25
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/behaviours/design-before-implementation@21cd568

Identify the decisions that could cause rework before implementing them. Match the design effort to the uncertainty and consequences.

Establish the contract

  • Inspect the current implementation, applicable instructions, and relevant tests before proposing a replacement.
  • State the requested outcome, affected interfaces, constraints, and how completion will be checked.
  • Separate independent deliverables only when that clarifies ownership, dependencies, or validation.
  • Ask about missing information only when it materially changes scope, authorization, data integrity, or a costly design choice. Continue independent work while waiting.

Choose and execute

Compare alternatives when a real tradeoff remains; do not manufacture options for a settled requirement. Record the selected approach and the assumption that would invalidate it.

An implementation request can already authorize routine design decisions and reversible edits. Do not insert a new approval gate solely because several files change. Honor an explicit design-only request and any actual restricted action.

For a substantial design, summarize the outcome, approach, interfaces/artifacts, validation, and unresolved decisions. Omit empty sections. A short explanation may suffice for a local change.

Load references/design-gates.md when reviewing a substantial design, testing its clarity with an independent reader, or resolving contradictory requirements.

Use software-architecture for module boundaries, public contracts, state ownership, and failure tradeoffs; implementation-planning when dependencies or a handoff warrant an executable plan; and verification-before-completion when reconciling delivered behavior with the design.

Files in this version

Permissions

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

Scan findings

Reviewed on Nov 13, 2026

  1. MediumPrompt injection · injection.no_confirmationreferences/design-gates.md:25
  2. InfoLink · Links to outside domains

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, 202621cd56873ba773dSigned–

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