namba-foundation-core

name	namba-foundation-core
description	Core NambaAI workflow, SPEC discipline, TRUST quality gates, and Codex-native execution rules.

Use this skill when the task involves NambaAI workflow orchestration, SPEC handling, quality gates, or phased delivery.

State effect: guidance plus execution support. Read-only when used for orientation; mutating only when the active Namba workflow is already executing.

Generated instruction contract for this repo skill:

• Purpose: keep the role or command scope explicit, bounded, and testable.
• Boundary: honor read-only versus mutating state effects, configured sandbox mode, and assigned file or workflow ownership.
• Required output: report concrete actions, changed paths or artifacts, validation evidence, and pass/fail status or blockers.
• Pass/fail criteria: claim success only when acceptance criteria and configured validation are satisfied; otherwise name the exact blocker and impact.
• Evidence expectations: cite source artifacts such as SPEC files, .namba/ configs, diffs, test output, PR/check links, or generated manifests instead of relying on unsupported assertions.
• Security responsibilities: never expose or commit secrets; treat auth, privacy, destructive commands, permission changes, and external network or credential use as security-sensitive.
• Destructive command and escalation policy: do not run destructive commands unless explicitly requested; request approval for privileged, networked, or sandbox-blocked actions only when the active approval mode allows it, and otherwise report the blocker or use a safe non-escalating path.
• Fallback implementer boundary: if a specialist path is unavailable and the main/default implementer takes over, stay within the assigned scope and preserve the same evidence and validation duties.
• Portability: keep durable guidance non-project-specific unless the current repository config or SPEC explicitly provides the project detail.

Key ideas:

• SPEC-first execution
• Codex-native implementation for namba run requests inside an interactive session
• TDD for greenfield or sufficiently tested projects
• DDD-style preserve/improve flow for brownfield projects with weak test coverage
• TRUST gates after each execution phase
• Worktree-based isolation for parallel work
• Namba report frame for substantial user-facing responses: scoped definition, judgment, work completed, current issues, potential risks, next steps