# Vibe Coding with Devin — From Executor to Cognitive Orchestrator > Markdown (GEO/AEO) version of . Author: **Mauricio Yokoyama Issei** · en-BR · Published: 2026-05-19 · Updated: 2026-10-10. ## In short O **Vibe Coding** Mature is not prompt chaos: it is **structured and persistent intention**. The human rises from executioner to **Cognitive Orchestrator** — directs the machine's intelligence with clear intent, like an executive chef who answers for each dish without cooking them all. - **Spec-Driven Development (SDD)** — the versioned specification is the reference of the intention: the AI implements against it, and differences between spec, tests and code are decided by people. - **BDD as verification** — Given/When/Then check the chosen behaviors; do not prove alone that the intention has been fulfilled. - **Arsenal Skills · Playbooks · Knowledge** — organizational knowledge that accumulates and re-uses itself in Git. - **A2UI** — the agent issues interface intent; rendering is governed and deterministic. ## The Practical Flow In the case study Devin + Salesforce, reported by the author, the flow has four steps: Spec (SDD definition of behavior) → Retrieve (autonomous context discovery) → Refactor (spec-guided edition) → Validar (Apex Tests that check the criteria of acceptance). The spec records the As-Is/To-Be, and tests make it verifiable under the contracts of the architecture layer. ## Frequently Asked Questions **What is Vibe Coding?** Vibe Coding is developing software driving an AI agent by intention instead of typing each line. In the mature form, the intention is structured and persistent (a versioned specification), not an ephemeral prompt — it is what separates the experiment from the method. **What is Spec-Driven Development (SDD)?** In SDD the versioned specification is the reference of intention: write what and why, and the AI implements against the spec, with tests (BDD) to verify. Spec is not infallible: when spec, tests and code differ, a person with authority decides what to correct. When the intention lives in a disposable prompt, it gets lost; in a spec version in the repository, it can be reviewed and audited. **What is the Cognitive Orchestrator?** It is the professional who directs the machine's intelligence with intent — defines what and why and judges the result — rather than executing each line. It consumes typed schema-derived tools and versiones not only the code, but the reasoning that produced it. **What are Skills, Playbooks and Knowledge?** It is the arsenal of organizational intelligence that grows over time: Skills are reusable procedures (refactoring without risk, testing exhaustively), Playbooks are process recipes (code review, onboarding, migration) and Knowledge is the asset that accumulates (architecture, conventions, lessons and drops). **What is A2UI (Agent-to-User Interface)?** It is the evolution of the MCP from the query to the rendering: the agent uses the protocol to issue interface intent — the Brain decides what to show (data under contract) and the deterministic display decides how to render. The interface ceases to be unpredictable free text and becomes ruled, testable and reproducible output. ## Glossary - **Vibe Coding** — Develop an agent by intention; in mature form, structured and persistent intention. - **SDD (Spec-Driven Development)** — The specification versioned as an intention reference; the AI implements against it and the tests verify the chosen behaviors. - **BDD** — Data/When/Then scenarios with recorded fixtures; tests the system around the model. - **Cognitive Orchestrator** — Who drives the machine's intelligence with intent, instead of running each line. - **A2UI (Agent-to-User Interface)** — The agent emits interface intent; the deterministic display decides how to render. *© 2026 Mauritius Yokoyama Issei. Citable content with assignment (fair use educational).*