SPECTION
DOCUMENTATION · docs/framework-guide.md
View source ↗

SPECTION Framework Guide

Purpose and audience

SPECTION helps developers, architects, students and teams build software that solves validated user problems. It combines specification-driven development, agent harnesses and evidence-based engineering. It supports both conventional applications and products integrating AI; an LLM is not a mandatory application dependency.

How the framework works

StageInputDeliverableGate
DiscoverBusiness idea, interviewsProduct Brief, success measuresStakeholder validates problem and scope
SpecifyReviewed briefPRD, RF/RNF IDs, acceptance criteriaRequirements reviewed and testable
ArchitectRequirementsHLD, ADRs, LLDTrade-offs and risks reviewed
PlanApproved featureFeature spec, plan, tasksDependencies and verification defined
BuildBounded tasksCode and testsReviewable changes; actual checks
VerifyImplementationTraceability and test evidenceAcceptance, security and human review
ReleaseReviewed incrementRelease notes, rollback, monitoringExplicit production approval
EvolveFeedback and incidentsUpdated specs and prioritized tasksChange impact reviewed

This is iterative, not a mandatory waterfall. Revisit specifications when evidence changes. Small changes can use lightweight documents; risky changes require deeper analysis.

Harness engineering

The harness is the context and control system around the AI model: AGENTS.md, approved specs, skills, tools, permission boundaries and feedback from tests. Feedforward guidance informs the agent before implementation; feedback checks detect issues afterward. Neither automatically proves correctness. Tool permissions must be enforced outside the model, not just requested in prompts.

Roles

The product owner validates value and scope; the developer owns implementation and evidence; architects review design trade-offs; security/privacy specialists assess material risk; a responsible human authorizes production. AI assists these roles, never substitutes for accountability.

Start

Use SPECTION Kit, the developer workflow, and the reference architecture. See responsible development for safeguards.