Skip to content

Stakeholder Persona: Lead Developer

Who is this for (2)
FieldValue
CategoryINTERNAL Stakeholder
Actor Typehuman
Primary GoalTranslate architecture and governance intent into practical implementation behavior.
Persona IDaud-lead-developer
Created / Updated2026-02-28 / 2026-11-13
Domain / ContextSpec Kitty 4.x
Statuscanonical

Overview

  • Role Focus: Delivery execution, code quality, and doctrine adoption.
  • Primary Function: Curates practices, validates feasibility, and applies governance decisions in implementation workflows.
  • Environment / Context: Several Missions in flight, each worked as work packages on lane branches or on a single Mission branch.

Core Motivations

  • Professional Drivers: Faster implementation with fewer ambiguous handoffs.
  • Emotional or Cognitive Drivers: Wants high signal in docs and low process overhead.
  • Systemic Positioning: Bridge between architecture intent and daily coding operations.

Desiderata

CategoryExpectation / NeedDescription
InformationActionable guidanceExpects architecture docs to clarify behavior, not restate code structure.
InteractionFast feedback loopsNeeds rapid validation for governance and workflow changes.
SupportReusable patternsPrefers patterns that can be applied across Missions without re-interpretation.
GovernanceExplicit activation rulesMust know when a curated practice is actually active (spec-kitty charter list, spec-kitty charter context --action <action>).
Decision AuthorityPractice adoption recommendationProposes and validates practical adoption paths before final approval.

Frustrations and Constraints

  • Pain Points: Policies that are unclear, duplicated, or disconnected from runtime commands.
  • Trade-Off Awareness: Accepts stronger process if it clearly reduces rework.
  • Environmental Constraints: Release timelines, mixed agent capabilities, and incomplete prior context.

Behavioral Cues

SituationTypical BehaviorInterpretation
Stable / RoutineOptimizes command workflowsImproves throughput through repeatable sequences.
Change / UncertaintyRequests concrete examplesUses examples to assess implementation realism.
Under PressureFocuses on deterministic minimum viable pathPrioritizes reliable completion over ideal abstractions.

Collaboration Preferences

  • Decision Style: Pragmatic and evidence-based.
  • Communication Style: Direct, implementation-oriented, and concise.
  • Feedback Expectations: Specific blockers, concrete alternatives, and clear acceptance criteria.

Design Impact

  • Affected By: Doctrine curation, charter activation (spec-kitty charter activate and deactivate), and validation gates.
  • Needs From Design: Clear ownership of transitions from proposal to active behavior.
  • Risk If Ignored: Shadow conventions and inconsistent implementation quality.
  • Acceptance Signal: Curated practices can be activated and observed without manual interpretation.

Measures of Success

DimensionIndicatorType
PerformanceTime from curated proposal to active practiceQuantitative
QualityDefect/rework rate after governance change adoptionQuantitative
GrowthTeam reuse of curated doctrine patternsQualitative

Narrative Summary

The Lead Developer operates where architecture decisions meet daily delivery. They need governance artifacts to be operationally useful and executable through commands, not just aspirational prose. Their trust increases when each policy change has a clear activation and validation path.