Christopher Clendening
96b7ff9766
- Create SECURITY.md to outline security policies and practices. - Establish WORKFLOW.md detailing the project lifecycle from planning to retrospective. - Introduce decision log structure in decisions/README.md for tracking architecture decisions. - Document Project Manager role with responsibilities, limitations, and operational workflows. - Implement templates for ADRs, bugs, meetings, projects, retrospectives, RFCs, roadmaps, and sprints. - Set up memory logs for architecture and company-wide lessons learned. - Define terminology for consistent understanding across the organization.
34 lines
881 B
Markdown
34 lines
881 B
Markdown
# Bug: <short title>
|
|
|
|
**Filed by:** QA Engineer (or whoever found it)
|
|
**Related Task:** link to Plane
|
|
**Severity:** Blocker | Major | Minor
|
|
|
|
## Expected behavior
|
|
|
|
What should have happened, per the Task's acceptance criteria.
|
|
|
|
## Actual behavior
|
|
|
|
What actually happened. State it plainly — this is not the place to soften a failure
|
|
(`EMPLOYEE_HANDBOOK.md` — never fabricate or round up results).
|
|
|
|
## Reproduction steps
|
|
|
|
1.
|
|
2.
|
|
3.
|
|
|
|
A bug filed without reproduction steps isn't actionable — QA reject authority
|
|
(`ORGANIZATION.md`) comes with the responsibility to make the rejection specific enough to act
|
|
on (`EMPLOYEE_HANDBOOK.md` review etiquette applies here too).
|
|
|
|
## Environment
|
|
|
|
Relevant runner (`ACT_RUNNER.md`), branch, commit SHA.
|
|
|
|
## Resolution
|
|
|
|
Filled in once fixed: linked PR, and confirmation that the regression test described in
|
|
`CODING_STANDARDS.md` was added.
|