.claude/skills/document-ahead-codingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Write documentation first, code second, for any non-trivial change to a codebase. Use when starting a new feature, refactor, bug fix, or migration; when multi-file work needs a reviewable plan; or right after a discuss-before-begin session has reached consensus. Keeps decisions, plans and the "why"
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/document-ahead-codingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/document-ahead-codingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/document-ahead-codingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @blueriverlhr/document-ahead-codingclawhub inspect @blueriverlhr/document-ahead-coding --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:b9ec62ed4ce4d2c7f54536e0a0ec0cae5b3b235b5c4f075fc2902a00917a9931skill-card.mdSKILL.md- Initial release of document-ahead-coding skill. - Introduces a workflow where documentation is written before coding for any significant codebase changes. - Defines clear directory structure (`docs/`) with subfolders for discussions, principles, tasks, manuals, and deferred decisions. - Establishes conventions for capturing discussions, reusable rules, task breakdowns, feature documentation, and rejected ideas. - Enforces "docs lead, code follows" and keeps documentation and code in sync. - Lists anti-patterns to avoid and provides scaling advice for tasks of different sizes.