القائمة
Zero Technical Debt skill for the ikigai project
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automated quality check loops with escalation and fix sub-agents
JSON-based end-to-end test format, runner, and mock provider
Jujutsu (jj) skill for the ikigai project
How to write effective Ralph goals for Ikigai-driven workflows
Create and manage Ralph goals from Ikigai using the real ralph-pipeline scripts
Create repositories using the real ralph-pipeline repo-create script
| name | zero-debt |
| description | Zero Technical Debt skill for the ikigai project |
Zero technical debt philosophy and work style principles for ikigai.
When you discover any problem, inconsistency, or standards violation:
Examples requiring immediate fixes:
When to ask first:
If you discover deficiencies in existing code while working nearby, fix them as part of your current work.
CRITICAL: Do not make architectural, structural, or refactoring changes unless explicitly requested.
Acceptable without asking:
check-compile, check-unit, check-filesize, check-complexityWhen discussing improvements: