liveBook · Manning

Minimum viable product

As explained in Claude at Work

A minimum viable product is an early implementation containing enough functionality to validate workflows and provide useful value.

A minimum viable product (MVP) is an early implementation focused on key workflows. In a greenfield build, it provides a useful component to test while keeping the first round of review manageable. It is not the complete service. section 5.9 section 5.11

Build and validate an MVP in small, reviewable steps:

  • Choose a component and identify the workflows needed for an early useful version. section 5.9
  • Inspect the design and codebase, resolve open decisions, and review the implementation plan before proceeding. section 5.10
  • Set a completion goal with testing gates. Run the service, explore its API, and inspect integration tests to build confidence in workflow coverage. section 5.10 section 5.11
  • Use what you learn to direct the remaining implementation, including any production-facing dependencies and additional quality gates. section 5.11

Start an authentication service

For an authentication service with multiple identity providers planned, first ask: “ready to implement src/services/auth - start with an MVP to get it running”. Review the proposed scope, including whether to use a stub identity provider. After approving the plan, set a goal: “/goal get the mvp working and tested with unit and integration tests”. Then review and exercise the result rather than treating the agent’s completion as proof of correctness. section 5.9 section 5.10

Listing 5.3 A REST Client file for exploring the API, generated by Claude
# Signing in

### Local-only sign-in: any email, no password, no IdP.
# @name login
POST {{host}}/api/v1/auth/dev-login
Content-Type: {{json}}

{
  "email": "ada@example.com",
  "displayName": "Ada Lovelace"
}

# Using the access token

### The signed-in user's profile.
GET {{host}}/api/v1/users/me
Authorization: Bearer {{login.response.body.$.accessToken}}

### The claims on the current token — no database read.
GET {{host}}/api/v1/auth/userinfo
Authorization: Bearer {{login.response.body.$.accessToken}}

This REST Client file exercises a local-only sign-in and uses the returned access token to check the profile and token claims. section 5.10

To move beyond the MVP, implement the remaining services in the design and replace the stub identity provider with a real one. For example, add Dex and OAuth Proxy to the Docker Compose setup, then run and test the full authentication stack. section 5.11

How Claude at Work covers it

How deep it goes
Walks through scoping, plan approval, testing, API exploration, and completion of an authentication service.
Examples
Uses an authentication service with local sign-in, token-based profile requests, and a later Dex integration.
What you can do after
Apply it via Claude Code to scope, build, test, and review an initial service implementation.
How it connects
Connects authentication and authorization with identity providers, automated testing, and API exploration.

Also explained in

Compare how 10 books explain minimum viable product →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Claude at Work. The section links point to the parts of the book it draws on.