Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Tzeusy/ai-bootstrap --skill broken-skillコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか?SkillsMP が現在取得できるファイルをダウンロードできます。
Use for project-level engineering governance in any repository — bootstrap or audit the knowledge architecture (doctrine, specs, topology, standards), concretize a feature request into a spec delta, amend a spec found wrong mid-implementation, reconcile specs against implementation, run a repo-wide health audit, decide what to work on next via spec-driven planning, milestone synthesis, and doctrine-grounded feature ideation, or run a recurring vision-pursuit audit that generates the next best moves toward the project's ideal. Route to exactly one subskill per task. Triggers: "project shape", "bootstrap docs", "what should we work on next", "should we build this", "I want to add X", "spec this feature", "the spec is wrong", "break this down", "review this project", "audit the codebase", "does the code match the spec", "what's the next milestone", "brainstorm features", "run the vision pursuit", "relentlessly improve this project".
Use when analyzing or bootstrapping the five-pillar knowledge architecture of a software project: about/heart-and-soul (doctrine), about/legends-and-lore (RFCs/design contracts), about/lay-and-land (topology), about/craft-and-care (execution-quality standards), and openspec/ (capability specs at root). Use when: starting a new project's knowledge structure, auditing documentation health, onboarding, deciding where knowledge belongs, or mapping system topology. Triggers: "project shape", "bootstrap docs", "where should this go", "what's this project about", "project pillars", "heart and soul", "spec structure", "knowledge architecture", "system map", "topology", "lay of the land", "set up project structure".
Use for engineering-quality work on any change or codebase — holding an implementation or review to the engineering quality bar, code readability, test-suite rigor, module boundaries and dependency chains, diagnosing hard bugs and flaky failures to root cause, post-refactor cruft cleanup, codebase documentation, creating or reviewing skills against the skill quality bar, or Excalidraw diagrams. Route to exactly one subskill per subdomain; fan out subagents when a task spans several. Triggers: "hold this to the engineering bar", "is this code readable", "review these tests", "untangle these dependencies", "diagnose this", "flaky test", "clean up this refactor", "document this service", "audit the docs", "review this skill", "draw a diagram".
SOC 職業分類に基づく
SKILL.md を表示中