YourTechBud/coding-harness-config
Command Claude Code
Author a structurally valid skill from requirements already settled in the conversation.
not rated 5
changed 1mo ago A 13 tokens
original Apache-2.0
5Stars on the repository
30Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
Apache-2.0Licence, which decides whether bodies are shown
YourTechBud/coding-harness-config
Command Claude Code
Brainstorm repo-specific engineering guidance, including UX, refactoring, observability, and review priorities.
not rated 5 yesterday A 19 tokens
original Apache-2.0
YourTechBud/coding-harness-config
Command Claude Code
Create a phase-wise implementation plan.
not rated 5
changed 1mo ago A 6 tokens
original Apache-2.0
YourTechBud/coding-harness-config
Command Claude Code
Use Socratic teaching to walk through and revise an implementation plan until its load-bearing design is understood, challenged, and internally consistent.
not rated 5 yesterday A 26 tokens
original Apache-2.0
YourTechBud/coding-harness-config
Command Claude Code
Review a change set against docs/engineering-guidance and return structured findings by severity (Blocker, Concern, Nit).
not rated 5 yesterday A 24 tokens
original Apache-2.0
plan-docs
06YourTechBud/coding-harness-config
Command Claude Code
Plan documentation changes from provided guidance.
not rated 5 yesterday A 6 tokens
original Apache-2.0
YourTechBud/coding-harness-config
Command Claude Code
Set up or revise a repo-local brainstorming artifact workspace under .isagi.
not rated 5 yesterday A 14 tokens
original Apache-2.0
verify-docs
08YourTechBud/coding-harness-config
Command Claude Code
Verify documentation against conversation context.
not rated 5 yesterday A 5 tokens
original Apache-2.0
YourTechBud/coding-harness-config
Command Claude Code
Write or refactor engineering guidance docs from the current conversation.
not rated 5 yesterday A 11 tokens
original Apache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: