feature-work SKILL.md skillA
feature-work from eltmon/overdeck is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eltmon/overdeck/feature-work@git:20260719.df80540Pins git:20260719.df80540 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eltmon/overdeck
- Path
sync-sources/skills/feature-work/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260719.df80540, committed Jul 19, 2026
- First version recorded
- May 22, 2026
- Size
- 1,116 bytes
- Repository stars
- 35
- License
- MIT
Standard workflow for implementing new features with testing.
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
# Feature Work When implementing a new feature: ## 1. Understand Requirements - Read the Linear/GitHub issue thoroughly - Check for an associated PRD draft at `<projectRoot>/.pan/drafts/<ISSUE-ID>.md` and the workspace xBRIEF at `.pan/spec.vbrief.json` - Identify acceptance criteria - Clarify ambiguities BEFORE coding ## 2. Design Approach - Identify files that need changes - Consider existing patterns in codebase - Plan implementation (don't gold-plate) ## 3. Implement - Follow existing code conventions - Make atomic, focused commits - Keep changes scoped to the issue - Commit format: `feat: description (ISSUE-XXX)` ## 4. Test - Add tests for new functionality - Run full test suite - All tests must pass before proceeding ## 5. Self-Review - Review your diff: `git diff origin/main...HEAD` - Check for: bugs, security issues, style, cruft - Fix issues found (don't just note them) ## 6. Submit - Push branch: `git push -u origin $(git branch --show-current)` - Create MR/PR with clear description
Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/feature-work@sha256:194a6d6ef520f730The line at the top of this page pins the label git:20260719.df80540, 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_cpm4eon67r2vyiug)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 22, 2026 and Jul 19, 2026, about one every 58 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260719.df80540 latest | 2026-07-19 | df80540 | 1,116 B | A | view · diff |
| git:20260522.817c2c7 | 2026-05-22 | 817c2c7 | 1,116 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 (1116 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
eltmon/overdeck · 35 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cpm4eon67r2vyiug GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/feature-work GET https://markdownregistry.com/api/v1/blob/194a6d6ef520f730f63ea011a8aa6d0b15df8d86877e6921ddefc09b187427a0
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.