Functional analysts live in the messy middle of software delivery. Before engineers can estimate, before QA can test, and before stakeholders can approve scope, someone has to translate raw product ambiguity into something the team can actually use. That work usually means writing: user stories acceptance criteria QA test cases risk matrices stakeholder summaries technical notes Jira-ready tickets It is valuable work, but it is also repetitive, time-consuming, and easy to underestimate. So for the Build With Gemma 4 DEV Challenge , I built Gemma Functional Analyst Copilot : a production-deployed AI workspace that uses Gemma 4 to accelerate software delivery documentation. Repository: github.com/olcesefacundo97/gemma-functional-analyst-copilot Live frontend: gemma-functional-analyst-copilot-cl.vercel.app Live backend: gemma-functional-analyst-copilot.onrender.com Production model: models/gemma-4-26b-a4b-it The Idea Most teams do not start with clean requirements.…