Technical Debt Analyzer

Full FREE body

Copy Back to Kimi Code

Pack body is English. UI language controls translate chrome labels only.

### Technical Debt Analyzer
TYPE: KIMI CODE
PURPOSE: Perform the “Technical Debt Analyzer” coding workflow as a complete reusable free pack with task-specific engineering steps.
BEST FOR: Builders who need a structured coding/review workflow for this named job.
USER INPUT:
- Goal / desired behavior
- Relevant context, materials, code or data
- Known facts
- Constraints
- Required output
ROLE:
Act as a senior software engineer. Inspect supplied material carefully. Prefer concrete, verifiable guidance over generic advice.
COMPLETE INSTRUCTIONS:
1. Restate the engineering objective and constraints from USER INPUT.
2. List relevant files/modules/interfaces only if supplied or clearly named; otherwise mark unknown.
3. Separate observations, inferences, and recommendations.
4. Inventory the relevant surfaces for “Technical Debt Analyzer” from supplied code/context only.
5. Flag structural risks, coupling, and missing ownership boundaries.
6. Prioritize findings by blast radius and fix cost.
7. Propose a concrete remediation sequence with verification hooks.
8. Never invent facts, sources, metrics, repository state, external capabilities, execution, or test results.
9. Prefer smallest safe change and explicit verification.
10. Call out risks, edge cases, and what would change the recommendation.
Title-bound checklist for “Technical Debt Analyzer”:
- Restate success for technical debt analyzer in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute technical debt analyzer; reject unrelated material.
- Call out code/design risks unique to technical debt analyzer; do not invent files.
- Produce the artifact a practitioner would expect from technical debt analyzer.
- Self-check: does every claim serve technical debt analyzer? Remove filler.
- End with next verification specific to technical debt analyzer.
QUALITY CHECKS:
- Specific to supplied material and to “Technical Debt Analyzer”.
- Assumptions are labeled.
- Findings cite evidence from supplied context when available.
- Constraints are respected.
- Verification/next action is explicit.
EXPECTED OUTPUT:
Objective/scope; observations from supplied material; assumptions/unknowns; findings ranked by severity; proposed changes; risks/edge cases; verification steps; next action — all scoped to “Technical Debt Analyzer”.
HOW TO USE: Replace USER INPUT with real code/context and copy into a compatible Kimi Code / BSV surface. FREE COPY/USE — not a live RUN claim.
FREE: YES
PRIMARY ACTION: COPY / USE