Menu
Write or refactor engineering guidance docs from the current conversation
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/YourTechBud/coding-harness-config --skill write-engineering-guidanceThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Create a phased, self-sufficient implementation plan from the current brainstorming context
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 the brainstorming skill, which supplies the session process. Invoke only when the user explicitly asks to shape or reshape epics or stories, work with Sparks, or configure issue-tracker persistence.
Based on SOC occupation classification
Showing SKILL.md
| name | write-engineering-guidance |
| description | Write or refactor engineering guidance docs from the current conversation |
Use the current conversation as the source of truth.
If the conversation has not yet converged on the guidance shape and key principles, stop and ask the user to continue with /brainstorm-engineering-guidance first.
<default_shape> Unless the conversation already settled on a better structure, start from:
docs/engineering-guidance/README.mddocs/engineering-guidance/core-principles.mddocs/engineering-guidance/how-to-use.mdAnd a small docs/engineering-guidance/lenses/ set, likely including:
You may add, merge, split, rename, or remove lens docs if that produces a better fit for the repo and the conversation.
If the brainstorm conversation produced severity calibration (Blocker / Concern / Nit) or rules for consuming the reviewer's Architectural Reflection channel, mention them briefly in how-to-use.md or inline where it's load-bearing. Do not invent calibration or consumption rules the conversation did not produce.
</default_shape>