The problem
Without stable context, each interaction may rediscover the project, repeat decisions and produce disconnected changes. A completed task list may still hide a failing flow.
I built modelo_projetos to make AI-assisted work a clear process: connected requirements, architecture, delivery and evidence. You can use and adapt this base too.
PATHS · PRD · ESCOPO · DECISOES
QUALITY_ROADMAP · DEMANDAS · TELAS
TESTES · BUGS · RUNBOOK · CHECKS
Without stable context, each interaction may rediscover the project, repeat decisions and produce disconnected changes. A completed task list may still hide a failing flow.
Keep a map of official sources, clear roles and delivery criteria. Read what matters, compare documents with code and connect each requirement to its evidence.
A team can explain what exists, what changed, how it was checked and what remains. The model supports that work. Quality still depends on adoption and review.
Review the kit, configure the map and make your first delivery.
WorkflowContext, SOLID, packages, batches, review and operations in one cycle.
ReferenceUnderstand each document’s role and when to read it.
ExamplesSee a requirement become code, tests and evidence.
DownloadsTemplates, validators, MIT license and bilingual instructions.
The base can guide a service, app, legacy system or product monorepo. It does not choose your architecture. You record real modules and commands, keep working conventions and adapt the policies.
The examples are educational. The download includes real validators, but needs setup and review in the adopted project.
Kit 1.0.0 · 35 files · MIT · 66 KB
It is a repository engineering and governance base. Documents define context and checks. Scripts help with inventory and validation. It does not replace your product or framework.
Yes. The kit uses the MIT license. Keep the copyright notice and license. You may adapt it to your team’s needs.
Yes. People can read and use the process. An assistant can help with work, but is not required to maintain documents, decisions and tests.
No. Checks verify only their own scope. Release, external integrations, restore, devices and human acceptance need their own evidence.
Not to use the kit. The ZIP includes adoption documents and scripts, without credentials or personal machine paths.