machinapractica/machina-practica
Phase-scoped project skills and evidence contracts for disciplined agent-assisted development.
Inspect project phase boundaries, provenance, and test evidence without modifying the repository; distinguish mechanical findings from semantic judgment.
Summarize an external game, protocol, business process, tool requirement, or source archive with traceable facts and ambiguities, before implementation design.
Define the first useful product journey and its UX, state, trust, recovery, and architecture after intent and platform are established; do not schedule implementation.
Turn an accepted MVP design into ordered, independently reviewable end-to-end tracer bullets with observable outcomes and evidence; do not invent product scope.
Route a project request to the appropriate Practica phase—vision, domain, scaffold, MVP design, plan, tracer, or read-only audit—while preserving the user’s requested scope.
Prepare a truthful blank application and production-build evidence for a chosen web, native, desktop, CLI, or service platform, before product architecture.
Implement one selected end-to-end outcome from an accepted plan, with ordinary-interface tests, compatibility evidence, and truthful status updates.
Write a project README and product vision from stated intent, keeping architecture, rules research, and delivery planning out of the initial phase.