メニュー
File a bug by adding a failing test case to the codebase marked as skipped with clear documentation. Use anytime the user reports a bug—create a test that reproduces it, mark it as skipped in the testing framework, and document the expected vs actual behavior.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Canonical reference for all contribution artifact schemas, templates, folder naming conventions, file format rules, and workflow patterns (progressive disclosure, two-gate system, constraint discovery, routing) used across dev-strategy workflow skills.
Enables structured contributions to dev-strategy implementation plans with proper documentation and knowledge transfer. Use when you need to "contribute to dev-strategy", "implement this phase", "review the code", "audit the implementation", "add to the dev plan", or make specialized contributions (testing, auditing, documenting) to existing dev-strategy roadmaps. Generates decision logs and context handoffs with mandatory documentation.
Creates sufficient implementation plans for complex coding projects by analyzing your codebase, gathering constraints, and proposing execution strategies. Use when you need to "plan how to build", "create implementation roadmap", "break down this feature", "how should I approach building", or structure multi-phase development, refactoring, or architectural changes. Produces code context, behavioral specs, decision logs, and implementation roadmaps.
Enables collaborative design contributions to dev-strategy implementation plans through human-in-the-loop sessions. Use when roadmap phases have "Design" objectives, you need to "design the [component]", "figure out the [approach]", "determine the [architecture]", or refinement before implementation. Works with `.plans/plan-[FEATURE-NAME]/` directories only. Produces lean design docs (< 100 lines) through interactive exploration with ruthless focus on simplicity.
Reference guide for design philosophy applied across all dev-strategy workflow skills. Use when you need to understand YAGNI, Last Responsible Moment, Kent Beck's 4 Simple Design Rules, Sufficient Design, and Just-In-Time Architecture principles. Provides context for planning, design, and implementation decisions.
Mandatory skill to use whenever you interact with any TUI built on the tui-harness/tui-elm/tui-design framework (diffviz-review-tui, patina-detect-tui, and future ELM-style TUIs in this workspace), whether to add code to it, test it, or plan a change
| name | Filing Bugs |
| description | File a bug by adding a failing test case to the codebase marked as skipped with clear documentation. Use anytime the user reports a bug—create a test that reproduces it, mark it as skipped in the testing framework, and document the expected vs actual behavior. |
A bug is successfully filed when:
@pytest.mark.skip, it.skip, #[ignore], etc.)tests/bugs/, bugs/ directory) if one existstests/bugs/issue_name.py)*_test.go, test_*.py, *.test.js, etc.)package.json, Cargo.toml, pyproject.toml, or equivalent for testing dependenciestests/bugs/, tests/regression/): Use ittests/bugs/ (for active bugs)tests/regression/ (for fixed bugs)# Bug: [Brief description of the bug]
# Expected: [What should happen]
# Actual: [What happens instead]
@pytest.mark.skip
def test_bug_something():
...