[realpython-bot]

Where to put new files:

• New files should go into a top-level subfolder, named after the article slug. For example: my-awesome-article

How to merge your changes:

1. Make sure the CI code style tests all pass (+ run the automatic code formatter if necessary).
2. Find an RP Team member on Slack and ask them to review & approve your PR.
3. Once the PR has one positive ("approved") review, GitHub lets you merge the PR.
4. 🎉

---

Sample code for the upcoming tutorial Spec-Driven Development With AI: A Hands-on OpenSpec Guide (draft: CMS Post 2521, Trello #1588). Files live in the sdd-openspec/ top-level folder, named after the article slug. Opened on behalf of Bartosz Zaczyński.

This replaces #883, which used the folder name openspec/ and linked a stale URL.

What's included

• sdd-openspec/source_code_initial/: The starter habits CLI (stdlib only, pytest for tests) that readers begin with, before OpenSpec is installed
• sdd-openspec/source_code_final/: The finished project after both changes in the tutorial, including the OpenSpec specs (habit-stats, habit-check-in), the archived changes (2026-10-11-add-stats-command, 2026-10-11-backdate-check-ins), openspec/config.yaml, and the .claude/ commands and skills generated by openspec init --tools claude (OpenSpec 1.14.1)
• sdd-openspec/README.md: Setup and usage

Checks

• ruff format --check and ruff check pass with ruff 0.14.1
• uv run --group dev pytest -q: 11 passed (initial), 39 passed (final), on Python 3.12 and 3.14
• openspec validate --all --strict passes in source_code_final/
• Replayed the tutorial with OpenSpec 1.14.1 on a copy of source_code_initial/: openspec init --tools claude regenerates byte-identical .claude/ files, and archiving both changes reproduces the openspec/ tree in source_code_final/ exactly

The opt-in sdd-openspec-code in the CMS should point at this sdd-openspec/ folder once merged.

🤖 Generated with Claude Code