Gabriel Brown
89761a7da3
Agent instructions, skills, SSH host aliases and expansion triggers are worth having identical on every machine one person owns, and belong in none of the shared configuration. They live in user/ now, with a manifest saying where each piece goes and a link-user stage that puts it there. That stage does nothing unless the machine said yes. Somebody who clones Panama to try the desktop keeps their own ~/.claude/CLAUDE.md exactly where it was; the question names the destinations and defaults to no. Anything displaced goes to config/old rather than being deleted. ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md were byte-identical copies of one file, which is the drift this exists to prevent. Also adds the vitals toggles for the battery and Claude usage readouts, which had preferences and no way to reach them.
15 lines
2.3 KiB
Markdown
15 lines
2.3 KiB
Markdown
# SOP for Development Review (KACP-23147, verbatim duties)
|
|
|
|
Developer Review Instructions. SOP for Development Review:
|
|
|
|
1. **Review the Epic.** Review the issues in this epic to ensure you understand what the requirements are. Reach out to the PM for clarification if needed.
|
|
2. **Handle Sprint Flag.** Assess whether a flag is needed for this Sprint, create it, and connect it to the Epic. Create the flag in LaunchDarkly (if applicable) and connect it to the Epic in the Releases field.
|
|
3. **Add development instructions.** For each issue in the epic, add development instructions using the Developer Review Instructions field. Follow the Developer Instructions template to provide clear, concise, and actionable guidance for the development team. Focus on providing context and information not already outlined in the task details to avoid redundancy.
|
|
4. **Add issue dependencies.** Identify and link dependent issues within the epic using the Blocks or is blocked by link type. Ensure that the issue dependencies are accurately represented to facilitate proper planning and execution.
|
|
5. **Provide time estimates.** Fill out the Original Estimate field for each issue in the epic. Provide your best estimate of how long each issue will take to complete, considering factors such as complexity, dependencies, and potential risks.
|
|
6. **Fill out the Risk Level.** Choose the appropriate Story Risk Level for each task in the epic. The Risk Level adds a buffer to the original estimate based on the task complexity, accounting for potential unknowns or challenges.
|
|
7. **Fill out the Testing Tab.** Based on the Technical Review and your assessment of the risks associated with each task, fill out the Risk Mitigation and Test Cases tables.
|
|
- Risk Mitigation: identify and list the risks associated with each task. Specify the mitigation strategy for each risk, which could include guidance on how to build the feature in a way that mitigates the risk, or outlining automated tests that need to be created to address the risk. If an automated test is required, create a subtask on the main task with the type of test and what it covers, and an estimate for the subtask.
|
|
- Test Cases: outline the manual test cases that the developer should execute to ensure the functionality works as expected and risks have been addressed.
|
|
8. Close this issue when finished.
|