Documentation
From a brief to a reviewed SDLC document set.
Alara Code turns an idea or an RFP into scope, requirements, design, test plan, compliance, traceability, a proposal and a delivery board — written by your project's agent, and reviewed by you before the pipeline moves on. These docs are for whoever is reading them: the people running projects, and the people running the product.
Getting startedYour first project, from an idea to an approved scope.Set up the project agentThe system prompt and the skill files every step needs.How the pipeline worksThe steps, the approval gates, and what a change upstream resets.
Start here
- What is Alara CodeThe product in one read: from an idea to a reviewed SDLC document set and a delivery board.
- Getting startedYour first project, end to end: create it, set up its agent, talk it through, and run the first steps.
- Key conceptsProjects, agents, skills, steps, gates, documents, versions and approvals — the words the rest of these docs use.
Using Alara Code
- ProjectsCreate a project, upload an RFP or start from an idea, and manage its settings, team and lifecycle.
- Set up the project agentCreate the Alara agent every step runs on: its system prompt, its skill files, and the readiness check.
- Talk to the agentShape your idea in the project chat, watch replies stream in, and turn the conversation into an RFP.
- Run the pipelineStart a step, follow it live in Summary or Raw, stop it, and understand what a failed step is telling you.
- Review, approve, request changesThe human gate after every step: read the draft, approve it or ask for changes, and what a new version resets.
- Read and export documentsThe Markdown reader, diagrams, the contents panel, the Markdown source, and exporting to PDF, Word, Excel, HTML or Markdown.
- The delivery boardEpics, stories and tickets from the /tasks step, laid out as a board you can move work across.
- Repository integrationConnect GitHub or Azure DevOps and push the approved documents and tickets into a repository.
- Run history and costsEvery run, who started it, how it ended, and what the agent's work cost.
- Members and permissionsWho can see a project, who can run, approve or stop a step, and how organization roles decide it.
The SDLC pipeline
- How the pipeline worksThe steps in order, the approval gates between them, and what happens downstream when an upstream document changes.
- RFPThe Request for Proposal: uploaded, or drafted by the agent from the project chat.
- ScopeObjectives, in- and out-of-scope items, constraints, assumptions, risks and deliverables, with SCOPE ids.
- SRS — requirementsThe IEEE 830 requirements specification: requirements, compliance flags, and a four-part narrative.
- SDS — designArchitecture, design components, decisions, APIs and data model, with the diagrams that explain them.
- STS — test planTest cases mapped to requirements and the IEEE 829 test plan around them.
- TasksEpics, stories and tickets for every design component — the delivery board's source.
- ComplianceRequirements checked against regulatory frameworks, with every gap flagged.
- TraceabilityThe matrix from requirement to feature, design component and test case — and where coverage is missing.
- ProposalThe client-facing proposal drawn from the approved documents.