> ## Documentation Index
> Fetch the complete documentation index at: https://felan.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# End-to-end SDLC

> Connect planning, implementation, review, testing, delivery, and operational follow-up through Felan sessions.

Felan can carry context across multiple stages of software work without forcing the team into a fixed pipeline. A session can begin with discovery, continue through repository changes and verification, and end with a delivery handoff. Separate automations can respond to later events.

## A practical flow

<Steps>
  <Step title="Frame the outcome">
    Give Felan the brief, constraints, connected repository, and definition of done. Ask it to identify missing decisions before implementation.
  </Step>

  <Step title="Plan the work">
    Use product and architecture context to produce a focused plan with affected areas, risks, and verification.
  </Step>

  <Step title="Implement and review">
    Ask Felan to make the approved repository changes, run targeted checks, and delegate independent review where useful.
  </Step>

  <Step title="Verify the result">
    Exercise the relevant behavior against the intended target and separate product defects, test issues, environment issues, and expected changes.
  </Step>

  <Step title="Prepare delivery">
    Summarize changed files, checks, evidence, risks, and follow-up actions for the team or connected workflow.
  </Step>

  <Step title="Respond after release">
    Use an event or scheduled [automation](/docs/platform/automations) to start a new session for deployment review, recurring verification, or operational follow-up.
  </Step>
</Steps>

## Keep control points visible

Felan’s available actions depend on team access and the request. State where approval is required, which environments are permitted, what evidence must be collected, and which external writes are in scope.

Use [Sessions](/docs/platform/sessions) for work that benefits from a continuous conversation. Use [Knowledge](/docs/platform/knowledge) for durable context shared across sessions, and use integrations to provide repository or external-system access.

<CardGroup cols={2}>
  <Card title="Software engineering" icon="code" href="/docs/use-cases/software-engineering">
    Explore implementation and review workflows.
  </Card>

  <Card title="Quality assurance" icon="flask" href="/docs/use-cases/qa">
    Add evidence-based verification to the lifecycle.
  </Card>
</CardGroup>