Menu
Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented.
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
Manage full-stack observability using Logfire (logging/tracing) and OpenObserve (storage/visualization).
Interface for managing the Temporal Database and AI system (ReDB + GGUF embeddings).
Spec-Driven Development workflow using VibesPro conventions
| name | implementation-guidance |
| description | Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards. |
| metadata | {"id":"ce.skill.implementation-guidance","tags":["execution","testing","validation"],"inputs":{"files":["PLAN.md","ARCHITECTURE.md","CONTRIBUTING.md"],"concepts":["small-diffs"],"tools":["toolset:write"]},"outputs":{"artifacts":["ce.task.validate"],"files":[],"actions":["apply-changes"]},"dependsOn":{"artifacts":["ce.task.validate"],"files":[".vscode/tasks.json"]},"related":{"artifacts":["ce.prompt.implement-step"],"files":[]}} |
This skill helps you turn a single plan step into code changes while following TDD and maintaining architectural integrity.
Select a plan slice. Identify the next unimplemented milestone or task from PLAN.md.
Summarise its objective, inputs, outputs and acceptance criteria.
Review constraints. Load ARCHITECTURE.md and CONTRIBUTING.md to understand any
constraints (e.g. design patterns, layer boundaries, security policies). Ensure your
implementation will not violate them.
Write tests first. Before writing production code, design unit and integration tests that express the desired behaviour. Use the testing strategy guidelines and harness appropriate frameworks.
Implement incrementally. Write small, focused commits that satisfy one test at a time. Avoid large diffs. Document significant decisions or deviations in an ADR if necessary.
Run validation and linting. After coding, execute the validation task (Context Kit: Validate)
and any language-specific linters or static analysis tools. Fix issues immediately.
Summarise changes. Prepare a concise summary of what was changed, which files were touched and how the acceptance criteria were met. Provide links to relevant docs or ADRs.
Handoff for review. Once the step is complete and validated, hand off to the reviewer
agent or trigger the review-changes prompt for quality assurance.
By following this process you produce maintainable code that is easy to review and less likely to introduce regressions or technical debt.
