Verify:Runner Core
The Runner Core team page.
Product Strategy and Roadmap
The product strategy and roadmap for the runner product categories are covered on the following direction pages.
Team Members
The following people are permanent members of the Verify:Runner Core group:
Stable Counterparts
Name | Role |
---|
Development Process
🔍 Spike Issues for Complex Work
If a task is too large, has too many unknowns, or requires proof of concept (POC), it should be broken down into smaller investigation tasks or POC issues. These tasks help clarify the scope, reduce risks, and identify the necessary steps to proceed with implementation.
Create an Investigation Issue
- Purpose: Research, investigate, and document or breakdown the necessary work. Clearly define the core question or problem you’re investigating.
- Label: Assign the ~spike label to the issue.
- Blocking Relationship:
- For issue investigations: Mark the investigation as blocking the original issue.
- For epic investigations: Add the investigation issue to the epic.
Close the Investigation
- Align with key stakeholders on findings and next steps. Consider using a sync meeting to make decisions together.
- Depending on the feedback, we can decide to allocate more time or settle for something that works based on the information we have.
- For Issue Investigations: Summarize findings in the investigation issue. The outcome should inform the implementation of the blocked issue. Update the blocked issues to now include a clear direction and acceptance criteria.
- For Epic Investigations: Break down and refine the epic into actionable issues. The outcome could include:
- Architecture Plan: High-level technical direction, quality goals (like performance, security), and supporting approaches.
- Iteration Plan: A breakdown of work into clearly scoped, refined issues.
- Add the plans to the epic description and close the investigation issue.
Last modified October 13, 2025: Typo fix in investigation process (
be60fef2
)