controlling-code-complexity
/controlling-code-complexity
Use when controlling code complexity is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
- Author
- Nolane-x ↗
- Repository
- forge-os ↗
- Licence
- MIT
- Last repository change
- 01.08.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when controlling code complexity is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Original author description
Use when controlling code complexity is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
How it works
- Overview
- Trigger
- Required Inputs
- Method-Specific Protocol
- Procedure
- Verification Questions
- Evidence Packet
- Output Contract
- Quality Gate
- Forbidden Shortcuts
SKILL.md preview
--- name: controlling-code-complexity description: "Use when controlling code complexity is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent." license: MIT compatibility: "ForgeOS-compatible Agent Skills hosts; no provider-specific model required." metadata: author: forgeos-community version: "0.2.0" pack: implementation kind: core status: candidate --- # Controlling Code Complexity ## Overview This skill owns one bounded responsibility: **controlling code complexity**. Its focus is controlling code complexity within implementation lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope. ## Trigger Activate only when the project is in one of these stages: `implementation`, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request. ## Required Inputs - `execution-plan` - `acceptance-contracts` - Current gate result, open findings, artifact hashes, and invalidation state - Required tools: `filesystem`, `shell` - Optional tools: none - Confirmed human decisions relevant to this scope ## Method-Specific Protocol 1. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by controlling code complexity. 2. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to controlling code complexity. 3. Apply controlling code complexity only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required. 4. Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers. 5. Create reproducible checks that would fail if controlling code complexity were incomplete or implemented incorrectly. ## Procedure 1. Load one task, its direct contracts, and its failing test. 2. Verify the test fails for the intended missing behavior. 3. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by controlling code complexity. 4. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to controlling code complexity. 5. Apply controlling code complexity only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required. 6. Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers. 7. Create reproducible checks that would fail if controlling code complexity were incomplete or implemented incorrectly. 8. Implement the minimum sufficient change. 9. Run focused tests, then relevant regression tests. 10. Review the diff for complexity, security, and contract drift. 11. Commit evidence and hand off to independent review. ## Verification Questions - Does the artifact make the owned decision for controlling code complexity explicit and bounded? - Are failure, recovery, permissions, concurrency, and irreversible side effects addressed where applicable? - Can every load-bearing claim be traced to a confirmed fact, direct artifact, executable check, or declared assumption? - Would a downstream agent know exactly what changed, what remains open, and what must be invalidated? ## Evidence Packet Produce or reference all applicable evidence: - `controlling-code-complexity-decision-table` - `controlling-code-complexity-verification-report` - `controlling-code-complexity-handoff-envelope` Evidence must identify the current artifact hash, command or method used, result, reviewer identity, timestamp, and limitations. ## Output Contract Produce: - `implemented-increment` The primary artifact must include schema version, provenance, consumed artifact IDs, decisions, evidence references, residual risks, validation state, and invalidation targets. Narrative explanation may accompany the artifact but cannot replace it. ## Quality Gate Reviewer: `independent-reviewer` - The output directly and completely performs controlling code complexity within its declared boundary. - Does the artifact make the owned decision for controlling code complexity explicit and bounded? - Are failure, recovery, permissions, concurrency, and irreversible side effects addressed where applicable? - Can every load-bearing claim be traced to a confirmed fact, direct artifact, executable check, or declared assumption? - Would a downstream agent know exactly what changed, what remains open, and what must be invalidated? - Every material claim is traceable to an input, decision, executable check, or evidence item. - Required fields are complete and machine-readable. - The producing agent is not the approving reviewer. - Open uncertainty and residual risk are explicit; critical findings are never hidden by an aggregate score. Pass only when: All mandatory rules pass, evidence targets the current artifact hash, and no unresolved critical finding applies. ## Forbidden Shortcuts - Do not infer a material requirement that the user has not confirmed. - Do not replace a typed artifact with a long explanation. - Do not approve work produced by the same agent identity. - Do not hide a critical failure behind a high aggregate score. - Do not load unrelated project history, files, references, or skill bodies. - Do not mark evidence complete when it targets a different artifact hash or version. ## Failure Modes - guessing a material requirement - producing prose without the contracted artifact - self-approving the output - expanding scope without a decision record - treating controlling code complexity as a naming exercise - covering only the happy path - creating extension points without a current contract or consumer ## Escalation and Invalidation Stop and request a human decision when scope, risk acceptance, irreversible action, cost ceiling, privacy boundary, or product direction is materially ambiguous. When this artifact changes, invalidate only descendants named by the artifact graph; preserve unaffected verified branches. ## Handoff - Next transition: the graph router selects a real consumer of `implemented-increment`. - Required evidence: `contract-validation`, `independent-review`, `controlling-code-complexity-decision-table`, `controlling-code-complexity-verification-report`, `controlling-code-complexity-handoff-envelope`. - Required envelope fields: `artifactId`, `schemaVersion`, `sha256`, `producingSkill`, `producingAgent`, `consumedArtifacts`, `decisionIds`, `evidenceIds`, `residualRisks`, `validationState`, `invalidationTargets`, `stopCondition`. - Stop condition: Output contract is satisfied, a blocker is recorded, or a material human decision is required. ## Token and Context Policy Load at most 8 direct artifacts and reference depth 1. Use stable IDs, hashes, signatures, and deltas instead of repeating full history. Use established domain terminology, state each requirement once, and spend context on decisions, code, tests, or evidence rather than narration. ## Reference Playbook Load [skills/references/core/implementation.md](../../../references/core/implementation.md) only when this skill needs pack-wide decision tables, evidence patterns, or cross-skill handoff rules. See `contract.json` for the machine-readable contract.
Files in this package (2)
- SKILL.md 7 KB
- contract.json 6 KB
Versions
The database has no other skills named controlling-code-complexity.
Database snapshot: 13.11.2026 · package version e7bf02f41f09 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90controlling-ai-cost
Use when controlling ai cost is required during ai-products product work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent. - 90reviewing-code-diffs
Use when reviewing code diffs is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.