القائمة
Track, categorize, and prioritize technical debt in a shared register.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | tech-debt |
| description | Track, categorize, and prioritize technical debt in a shared register. |
| argument-hint | [scan|add|prioritize|report] |
| user-invocable | true |
Purpose: Keep one visible, practical register of technical debt and its urgency.
Use when:
Do not use for:
Inputs / Required Context:
scan|add|prioritize|reportadd: description, affected area, acceptance reason, and practical impactOutputs / Owned Artifacts:
docs/tech-debt-register.mdModes or Arguments:
scan: inspect the codebase and add clearly actionable debt itemsadd: record one explicit debt itemprioritize: reorder or regroup the register by practical urgencyreport: summarize the current registerExecution Rules:
scan, look for high-signal indicators such as TODO, FIXME, duplication, risky untested logic, oversized code, or stale docs.prioritize, sort by impact, frequency, blast radius, and fix cost.report, summarize totals, oldest unresolved items, and debt that should move into the next cycle.Failure / Stop Conditions:
add if the item lacks a concrete description or affected areaReturn Format:
Example Invocation:
/tech-debt scanRelated Skills / Boundary:
architecture-decision when debt resolution requires a durable architectural choiceAudit game assets against naming, size, format, and reference integrity rules.
Implement one approved game system in production-facing project code.
Define the first audience-facing demo contract from a proven playable MVP and route the follow-up UI, asset, and presentation work.
Write or update a game-system GDD using the canonical gamedev template.
Decompose a game concept into systems, map dependencies, and maintain the systems index.
Choose a game engine or runtime direction and create a project technical-preferences document from the canonical gamedev template.