Claude Code is already capable. iSDLC adds structure, control, and traceability on top.
Claude Code already executes well — it spawns parallel agents, runs tests, retries on failure, and reviews its own work. iSDLC adds structured phases, user-defined guardrails, and configurable control over how all of that happens.
CLAUDE CODE — Native Execute
Capable, Self-Directed
⚡
Capable execution — spawns parallel agents, uses agent teams, edits multiple files concurrently. Not limited to linear edits
🧪
Testing is Claude-directed — Claude decides when and how to test. TDD and ATDD are possible but not structurally enforced — no user control over test strategy
👀
Review is Claude-directed — Claude reviews its own work, but the developer has limited structured control over review criteria or coverage checks
🔄
Retries on failure — Claude retries when things break, but the retry strategy, escalation path, and circuit-breaker thresholds are not user-configurable
📝
No structured audit trail — work is captured in git history but not connected to requirements, acceptance criteria, or a traceable task plan
→
iSDLC — Build (adds structure)
Structured, User-Controlled
🏗️
Defined phases — test strategy → implementation → quality loop → code review. Each phase has a dedicated specialist, clear entry/exit criteria, and gates
🧪
Test-first enforced — the test strategy phase runs before implementation begins. The quality loop iterates until tests AND automated QA both pass. The team controls the coverage thresholds
🛡️
User-defined guardrails — constitutional validation, blast-radius coverage, iteration corridors. 36 runtime guardrails, all configurable by the team
🔄
Controlled retry + escalation — configurable retry limits per gate, circuit-breaker thresholds, and explicit escalation to human when automated retries are exhausted
⚡
Dependency-ordered parallel dispatch — tasks from the analysis plan are sorted into tiers and dispatched in parallel, with dependency tracking and per-task traceability
📊
Full traceability — every task traces to acceptance criteria. Every change traces to the task plan. Every review is recorded against defined check categories
iSDLC Provides Structure to Claude Code
Claude Code is the engine. It spawns agents, edits files, runs tests, retries on failure, reviews code. These are powerful capabilities. iSDLC does not replace any of them — it adds a structured layer on top that gives teams control over how those capabilities are applied.
For tactical work — quick fixes, exploratory changes, one-off refactors — Claude Code's native capabilities are the right tool. Plan mode, direct execution, ad-hoc testing. Fast and flexible.
For structured work — features, bugs, and changes significant enough to warrant requirements, design, testing, review, and traceability — iSDLC provides the phases, the guardrails, the confirmation gates, and the audit trail that keep multi-file, multi-hour work consistent and traceable.
The trivial tier is the bridge — when analyse concludes a change is small enough, the build skips the full workflow and executes with Claude Code's native capabilities plus a lightweight audit trail. The framework adapts to scope, not the other way around.
The extensibility is the differentiator — the constitution, the perspectives, the skills, the guardrails, and the finalization checklist are all configuration-driven and hackable. Teams shape the framework to their standards; the framework doesn't impose a one-size-fits-all process.
In practice, they stack: Discover sets up the project knowledge → Embeddings enable semantic search → Test Generate captures existing behaviour → Add tracks work items from GitHub or Jira → Analyse produces the spec through interactive conversation → Build executes the spec automatically. Each stage's output feeds the next. Plan mode and native execute remain available for ad-hoc work between workflow runs.