Create a phased, self-sufficient implementation plan from the current brainstorming context
YourTechBud/coding-harness-config
SkillsMP has collected 37 skills from YourTechBud/coding-harness-config. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 37
- GitHub stars
- 5
- GitHub forks
- 2
Skills in this repository
Showing 37 of 37 collected skills.
Create a phased, self-sufficient implementation plan from the current brainstorming context
Domain companion for product issue shaping — turns raw Sparks and project context into sequenced active and candidate epics with acceptance-oriented stories, reshapes existing epic scope, and supports repository-specific issue-tracker persistence. Pairs with…
Domain companion for product issue shaping — turns raw Sparks and project context into sequenced active and candidate epics with acceptance-oriented stories, reshapes existing epic scope, and supports repository-specific issue-tracker persistence. Pairs with…
Domain companion for product issue shaping — turns raw Sparks and project context into sequenced active and candidate epics with acceptance-oriented stories, reshapes existing epic scope, and supports repository-specific issue-tracker persistence. Pairs with…
Explain a bounded subject from supplied source material and a comprehension objective with concise diagrams, code-shape sketches, and focused representations. Invoke only when explicitly asked to show or explain something visually.
Create a story-scoped, evidence-backed current-state analysis of an existing codebase for downstream architecture and program design. Invoke only when explicitly asked to analyze current state.
Author a structurally valid skill from requirements already settled in the conversation
Create a story-scoped target architecture from current-state analysis for downstream program design. Invoke only when explicitly asked to design architecture.
Create a story-scoped program design from current-state and architecture artifacts for downstream implementation planning. Invoke only when explicitly asked to design the program.
Create a story-scoped, evidence-backed current-state analysis of an existing codebase for downstream architecture and program design. Invoke only when explicitly asked to analyze current state.
Author a structurally valid skill from requirements already settled in the conversation
Create a story-scoped target architecture from current-state analysis for downstream program design. Invoke only when explicitly asked to design architecture.
Create a story-scoped program design from current-state and architecture artifacts for downstream implementation planning. Invoke only when explicitly asked to design the program.
Create a story-scoped, evidence-backed current-state analysis of an existing codebase for downstream architecture and program design. Invoke only when explicitly asked to analyze current state.
Create a story-scoped target architecture from current-state analysis for downstream program design. Invoke only when explicitly asked to design architecture.
Create a story-scoped program design from current-state and architecture artifacts for downstream implementation planning. Invoke only when explicitly asked to design the program.
Use Socratic teaching to walk through and revise an implementation plan until its load-bearing design is understood, challenged, and internally consistent
Use Socratic teaching to walk through and revise an implementation plan until its load-bearing design is understood, challenged, and internally consistent
Thinking-partner skill for co-building shared understanding before action. Invoke only when the user explicitly asks to brainstorm, e.g. "brainstorm" or "let's brainstorm this". Do not invoke for ordinary requests that merely involve thinking, design,…
Review a change set against docs/engineering-guidance and return structured findings by severity (Blocker, Concern, Nit)
Review a change set against docs/engineering-guidance and return structured findings by severity (Blocker, Concern, Nit)
Brainstorm repo-specific engineering guidance, including UX, refactoring, observability, and review priorities
Brainstorm repo-specific engineering guidance, including UX, refactoring, observability, and review priorities
Domain companion for interface, interaction, and visual work — refocuses on the underlying user problem, infers taste from the existing product rather than a generic playbook, and explores 2–5 meaningfully distinct variants the user can see instead of prose…
Domain companion for interface, interaction, and visual work — refocuses on the underlying user problem, infers taste from the existing product rather than a generic playbook, and explores 2–5 meaningfully distinct variants the user can see instead of prose…
Domain companion for interface, interaction, and visual work — refocuses on the underlying user problem, infers taste from the existing product rather than a generic playbook, and explores 2–5 meaningfully distinct variants the user can see instead of prose…
Write or refactor engineering guidance docs from the current conversation
Write or refactor engineering guidance docs from the current conversation
Generate a reviewer's orientation guide (HTML) for a changeset to make human review faster
Generate a reviewer's orientation guide (HTML) for a changeset to make human review faster
Plan documentation changes from provided guidance
Set up or revise a repo-local brainstorming artifact workspace under .isagi
Verify documentation against conversation context
Plan documentation changes from provided guidance
Set up or revise a repo-local brainstorming artifact workspace under .isagi
Verify documentation against conversation context