A practical flow
1
Frame the outcome
Give Felan the brief, constraints, connected repository, and definition of done. Ask it to identify missing decisions before implementation.
2
Plan the work
Use product and architecture context to produce a focused plan with affected areas, risks, and verification.
3
Implement and review
Ask Felan to make the approved repository changes, run targeted checks, and delegate independent review where useful.
4
Verify the result
Exercise the relevant behavior against the intended target and separate product defects, test issues, environment issues, and expected changes.
5
Prepare delivery
Summarize changed files, checks, evidence, risks, and follow-up actions for the team or connected workflow.
6
Respond after release
Use an event or scheduled automation to start a new session for deployment review, recurring verification, or operational follow-up.
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 for work that benefits from a continuous conversation. Use Knowledge for durable context shared across sessions, and use integrations to provide repository or external-system access.Software engineering
Explore implementation and review workflows.
Quality assurance
Add evidence-based verification to the lifecycle.