Files
nt8-sdk/.kilocode/rules/development_workflow.md

2.2 KiB

NT8-SDK Development Workflow

Last Updated: 2026-04-05

Operational workflow for Kilo/Codex-assisted development.

Per-Task Workflow (Required)

  1. Confirm scope
    • Confirm exact files allowed by task spec.
    • Cross-check .kilocode/rules/file_boundaries.md.
  2. Set task state
    • Move task status from todo -> doing before edits.
  3. Implement
    • Make minimum-diff changes only in scoped files.
  4. Verify
    • Run .\verify-build.bat per .kilocode/rules/verification_requirements.md.
    • Run focused tests required by changed area.
  5. NT8 compile/deploy checks (when NinjaScript files are touched)
    • Validate signatures against official NT8 docs.
    • Run repo build/deploy sequence required for NT8.
    • Compile in NinjaScript Editor (authoritative NT8 check).
  6. Documentation updates
    • Update docs/00-governance/active_work.md when task status or blockers changed.
    • Update docs/00-governance/roadmap.md when sequencing/scope changed.
    • Update docs/00-governance/decisions.md when durable architecture decisions were made.
    • Update CLEANUP_LOG.md when cleanup debt status changed.
  7. Compile-learning capture (if any compile issue occurred)
    • Add prevention rule to docs/00-governance/compile_guardrails.md.
    • Add error fingerprint + fix to docs/00-governance/common_failures.md.
    • Add pattern/anti-pattern to docs/00-governance/patterns_and_antipatterns.md.
  8. Set task state and report
    • Move task status from doing -> review.
    • Report changed files and verification evidence.

Definition of Done (Required)

  • Only scoped files changed.
  • Verification gates passed.
  • NT8 compile checks completed when relevant.
  • Relevant governance docs updated.
  • Compile learnings captured when applicable.
  • Task moved to review with evidence.

Out-of-Scope Safety

  • Do not modify files outside task scope.
  • Do not apply opportunistic refactors.
  • Do not modify historical/contextual docs unless explicitly requested.
  • If a real fix needs out-of-scope changes, stop and report a scope blocker.