Learn why to discuss technical design before implementation SKILL.md skillA
Learn why to discuss technical design before implementation from intai/story-flow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add intai/story-flow/Learn why to discuss technical design before implementation@git:20260811.7c0af34Pins git:20260811.7c0af34 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- intai/story-flow
- Path
plugins/junior-flow/skills/learn-technical-design/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260811.7c0af34, committed Aug 11, 2026
- First version recorded
- Feb 2, 2026
- Size
- 7,738 bytes
- Repository stars
- 16
- License
- MIT
Interactive guidance on creating technical design PRs to align with your team before coding.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Why Discuss Technical Design Before Implementation? ## Overview This learning module helps junior developers understand why creating a technical design PR before implementation leads to better outcomes, faster delivery, and reduced rework. ## Instructions Present the following content interactively. After each section, use `AskUserQuestion` to offer 3 options: - "Continue to next section" - "Show me an example" - "I have a question" --- ## Section 1: The Purpose of Technical Design PRs Explain that in story-flow, before writing implementation code, developers create a pull request containing their technical design: **A technical design PR serves three purposes:** 1. **Early feedback on approach** - Get team input before investing time in implementation 2. **Alignment before coding** - Ensure everyone agrees on the direction 3. **Living documentation** - The merged design becomes part of the repo history **The key insight:** > A technical design PR is not about seeking permission. It's about leveraging collective expertise to find the best solution before committing to an approach. **What gets included:** - Story requirements (from the story tracker, Figma analysis) …
Read the whole file at its exact version.
How to install
mdr add intai/story-flow/Learn why to discuss technical design before implementation@sha256:d15526b5e730caa9The line at the top of this page pins the label git:20260811.7c0af34, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_76znohu476enzc2a)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 2, 2026 and Aug 11, 2026, about one every 48 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260811.7c0af34 latest | 2026-08-11 | 7c0af34 | 7,738 B | A | view · diff |
| git:20260522.6ae8169 | 2026-05-22 | 6ae8169 | 7,737 B | A | view · diff |
| git:20260216.ed289a5 | 2026-02-16 | ed289a5 | 7,713 B | A | view · diff |
| git:20260202.7a9fda9 | 2026-02-02 | 7a9fda9 | 7,691 B | A | view · diff |
| git:20260202.039b380 | 2026-02-02 | 039b380 | 7,689 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7738 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
intai/story-flow · 16 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_76znohu476enzc2a GET https://markdownregistry.com/api/v1/resolve?ref=intai/story-flow/Learn why to discuss technical design before implementation GET https://markdownregistry.com/api/v1/blob/d15526b5e730caa9dafc4385cf68a0043734bb64d8d9f7060a87745d9d95ee02
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.