diff --git a/commands/extract.md b/commands/extract.md
index 36a388a..95ac910 100644
--- a/commands/extract.md
+++ b/commands/extract.md
@@ -215,11 +215,22 @@ Create new files in `dev/adr/` using this format:
 ### Knowledge updates
 
 For each knowledge update:
-1. Read the full target file
+1. Read the full target file (or create a new one if needed)
 2. Find the appropriate section (match by heading)
 3. Add or update content within that section
 4. If the section does not exist, create it in a logical position
-5. Add a source marker: `<!-- Extracted from specs/<spec-name> on YYYY-MM-DD -->`
+5. Add a source marker: `<!-- Extracted from specs/archive/<spec-name> on YYYY-MM-DD -->`
+
+If creating a new knowledge file, follow the standard structure:
+```markdown
+# <Topic>
+
+## Overview
+
+<Brief description of what this document covers.>
+
+## <Sections...>
+```
 
 ### Guidelines updates
 
@@ -227,7 +238,7 @@ Same approach as knowledge updates:
 1. Read the full target file (or create a new one if needed)
 2. Find the appropriate section
 3. Add the prescriptive pattern with code examples where relevant
-4. Add a source marker: `<!-- Extracted from specs/<spec-name> on YYYY-MM-DD -->`
+4. Add a source marker: `<!-- Extracted from specs/archive/<spec-name> on YYYY-MM-DD -->`
 
 If creating a new guidelines file, follow the standard structure:
 ```markdown
diff --git a/commands/prep.md b/commands/prep.md
index 2eb5816..cbcde31 100644
--- a/commands/prep.md
+++ b/commands/prep.md
@@ -67,7 +67,7 @@ Inspect `$ARGUMENTS`. The check is **only meaningful when the user provided a su
 
 1. **`$ARGUMENTS` contains one or more URLs** (links to a Notion / Confluence / Google Doc / GitHub issue / Linear ticket / shared Markdown / PDF). Treat each URL as a likely PRD location. **Run the check.**
 2. **`$ARGUMENTS` itself looks like a detailed PRD** — multiple paragraphs with structure such as headings, bullet lists of requirements, explicit goals/non-goals, acceptance criteria, or > ~400 characters of substantive description. **Run the check.**
-3. **`$ARGUMENTS` is a one-line description, vague brief, or empty.** **Skip the check** — there is no source-of-truth document to align against. Write a short note in your final summary stating you skipped this phase and why, and proceed to Completion.
+3. **`$ARGUMENTS` is a one-line description, vague brief, or empty.** **Skip the check** — there is no source-of-truth document to align against. Write a short note in your final summary stating you skipped this phase and why, and proceed to Completion. If the input is short (under ~400 characters) but still carries substantive, requirement-bearing detail, use your judgment and treat it as a PRD under rule 2 rather than skipping.
 
 #### 5b. Resolve the source-of-truth PRD