diff --git a/specs/666-sample-markdown-document-1d215a/feature.yaml b/specs/666-sample-markdown-document-1d215a/feature.yaml
new file mode 100644
index 000000000..360be318d
--- /dev/null
+++ b/specs/666-sample-markdown-document-1d215a/feature.yaml
@@ -0,0 +1,33 @@
+feature:
+  id: "666-sample-markdown-document-1d215a"
+  name: "sample-markdown-document-1d215a"
+  number: 666
+  branch: "feat/666-sample-markdown-document-1d215a"
+  lifecycle: "research"
+  createdAt: "2026-04-18T22:08:57Z"
+status:
+  phase: "research"
+  progress:
+    completed: 0
+    total: 0
+    percentage: 0
+  currentTask: null
+  lastUpdated: "2026-04-18T22:08:57Z"
+  lastUpdatedBy: "feature-agent"
+  completedPhases:
+    - "fast-implement"
+validation:
+  lastRun: null
+  gatesPassed: []
+  autoFixesApplied: []
+tasks:
+  current: null
+  blocked: []
+  failed: []
+checkpoints:
+  - phase: "feature-created"
+    completedAt: "2026-04-18T22:08:57Z"
+    completedBy: "feature-agent"
+errors:
+  current: null
+  history: []
diff --git a/specs/666-sample-markdown-document-1d215a/spec.yaml b/specs/666-sample-markdown-document-1d215a/spec.yaml
new file mode 100644
index 000000000..1b5f83462
--- /dev/null
+++ b/specs/666-sample-markdown-document-1d215a/spec.yaml
@@ -0,0 +1,55 @@
+# Feature Specification (YAML)
+# This is the source of truth. Markdown is auto-generated from this file.
+
+name: sample-markdown-document-1d215a
+number: 666
+branch: feat/666-sample-markdown-document-1d215a
+oneLiner: create a single markdown file called test-s7ry8n.md with a title and 2-3 sentences about anything
+userQuery: >
+  create a single markdown file called test-s7ry8n.md with a title and 2-3 sentences about anything
+summary: >
+  create a single markdown file called test-s7ry8n.md with a title and 2-3 sentences about anything
+phase: Analysis
+sizeEstimate: M
+
+# Relationships
+relatedFeatures:
+  []
+
+technologies:
+  []
+
+relatedLinks:
+  []
+
+# Open questions (must be resolved before implementation)
+openQuestions:
+  []
+
+# Markdown content (the actual spec)
+content: |
+  ## Problem Statement
+
+  create a single markdown file called test-s7ry8n.md with a title and 2-3 sentences about anything
+
+  ## Success Criteria
+
+  - [ ] TBD
+
+  ## Affected Areas
+
+  | Area | Impact | Reasoning |
+  | ---- | ------ | --------- |
+  | TBD  | TBD    | TBD       |
+
+  ## Dependencies
+
+  None identified.
+
+  ## Size Estimate
+
+  **M** - To be refined during research
+
+  ---
+
+  _Generated by feature agent — proceed with research_
diff --git a/test-s7ry8n.md b/test-s7ry8n.md
new file mode 100644
index 000000000..e9c4740cd
--- /dev/null
+++ b/test-s7ry8n.md
@@ -0,0 +1,3 @@
+# The Art of Documentation
+
+Clear documentation is essential for any successful project. It serves as a bridge between developers, users, and stakeholders, ensuring everyone understands the purpose and functionality of the system. Well-written documentation can significantly reduce onboarding time and help prevent bugs by providing clear guidelines for implementation.