codex-claude-mcp: Skill for Claude Code

Execute a Noodle Seed implementation plan

Execute an approved plan without reopening settled design decisions. Keep implementation, review, and evidence scoped to the current repository and the authority the user granted.

Preconditions

• Read the plan, repository instructions, current branch status, and the files named by the first incomplete task.
• Confirm the plan is decision-complete, test-first, compatible with the current code, and explicit about public contracts and required verification.
• Work in the repository-required isolated branch or worktree and preserve unrelated changes.
• If current code invalidates the plan or two requirements conflict, stop before editing and ask which requirement governs.

Task loop

Execute one task at a time in plan order:

1. Restate the task boundary, expected behavior, focused failing test, and files in scope.
2. Add or update the focused test first and run it to confirm the expected failure when practical.
3. Implement only the behavior required to make that test pass. Do not add compatibility paths, abstractions, or adjacent cleanup the plan did not require.
4. Run the focused test, then the package-level checks named by the plan.
5. Review the task diff for plan compliance, correctness, security, type safety, and unnecessary surface area.
6. Record completion in the plan checkbox when it is writable and in a focused conventional commit.

When the active host provides isolated task workers and user authorization permits delegation, use a fresh implementer for an independent task and a separate reviewer after it. Give each worker only the task requirements, binding global constraints, file paths, and required evidence. Never run workers in parallel when their files or contracts overlap. Execute inline when workers are unavailable, tasks are tightly coupled, or delegation is not authorized.

Review and recovery

• Independent review must compare the task requirements with the exact task diff and test evidence; implementer self-review does not replace it when a reviewer is available.
• Return concrete findings to the implementer, rerun the tests that cover each correction, and review the correction diff again.
• Allow at most three correction rounds for the same finding. Then stop with the unresolved requirement, attempted fixes, and current evidence instead of silently accepting drift.
• On context loss or interruption, resume from the plan checkboxes, git status, and git log; verify the last completed task before starting the first incomplete one.