Start & Adopt

New Software Flow

Build the first feature from reviewed specifications and architecture guidance. Reuse that context as your coding agent implements the next feature.

Start with Reqode

Start with one new capability

Define the first customer portal capability in a separate FieldDesk branch. The new module starts with no requirements.

From product idea to verified implementation

Establish intent and architecture before the first implementation pass.

Start with one product slice. Keep its requirements, implementation and verification evidence connected.

Add subsystems

Define backend, frontend, workers, or other technical boundaries. Connect repositories when available and use presets for a known stack.

Connect repositories when they exist.

Use presets when the stack or subsystem set is already known.

Define the architecture contract

Use AI Architect to prepare each subsystem’s Code Manifest and Unit Types: naming, folder structure, execution flow, testing expectations, and allowed specification relations.

Document naming, folder structure, execution flow, testing expectations, and allowed spec relations.

Create the product model

Prepare requirements, data, UI, and API specifications with AI Analyst. Review, edit, or disable proposed items before Apply.

AI output remains reviewable until Apply.

The team edits or disables speculative items before they become product truth.

Implement

Give the coding agent the Change Request key. It retrieves the accepted specifications and architecture guidance through MCP. Map the implementation to software units.

Findings show whether the fix belongs in code, specs, units, or architecture guidance.

Verify

Run scoped alignment and guideline checks, then execute requirement-linked tests. Review Findings and results, correct gaps, and keep the accepted context for the next feature.

Findings show whether the fix belongs in code, specs, units, or architecture guidance.

The foundation for the next feature

The first feature establishes specifications, architecture, implementation links, and test evidence that later changes can build on.

Product specs

Requirements, actors, data entities, user interfaces, wireframes, API surfaces, API operations, and specification relations.

Architecture contract

Subsystems, Code Manifest, Unit Types, allowed spec relations, repository mappings, and architecture rules for AI coding.

Implementation package

Change Requests connect scope, branch, affected specs, affected subsystems, AI sessions, and implementation instructions.

QA and verification

Test cases, software units, unit-to-spec links, alignment checks, guideline checks, and Findings after implementation.

Good First Artifacts

Define enough context for one feature. Expand the model as the product grows.

Requirements model

Main actors, requirement and specification types.

A focused module with the requirements needed for the first feature.

Specification core

Core data entities and attributes.

First API surface and key operations.

First user interfaces, transitions, and wireframes.

Implementation control

Main subsystems with code manifest for each.

Unit Types for expected architecture roles.

First Change Request, software units, and QA test cases.

Ready to Start New Software with Reqode?

Prepare one feature, implement it with your agent, and review its results before extending the product.