99 lines
3.8 KiB
HTML
99 lines
3.8 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
<title>Update Board — Roject</title>
|
|
<link rel="stylesheet" href="../../_assets_/styles.css">
|
|
<link rel="stylesheet" href="../../_assets_/nav.css">
|
|
</head>
|
|
<body>
|
|
<div class="page">
|
|
|
|
<header>
|
|
<h1>Update Board</h1>
|
|
<p class="subtitle">Review what was done in this session and keep the three boards accurate.</p>
|
|
</header>
|
|
|
|
<section>
|
|
<h2>Summary</h2>
|
|
|
|
<div class="card">
|
|
<p>
|
|
At an appropriate point in a working session, read the boards and the recent git
|
|
history, then propose which items should move, be added, or be removed.
|
|
Present the proposal to the user first. Only after approval, apply the changes.
|
|
Never move items silently.
|
|
</p>
|
|
</div>
|
|
</section>
|
|
|
|
<section>
|
|
<h2>Steps</h2>
|
|
|
|
<div class="card">
|
|
<h3>Step 1 — Read the current state</h3>
|
|
<p>Read all three board files:</p>
|
|
<pre><code>workspace/boards/tasks.html
|
|
workspace/boards/bugs.html
|
|
workspace/boards/backlog.html</code></pre>
|
|
<p style="margin-top:0.75rem">
|
|
Also read the recent git log and the current session's history entry (if one exists)
|
|
to understand what was actually completed.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="card">
|
|
<h3>Step 2 — Propose changes</h3>
|
|
<p>
|
|
Present a clear proposal to the user before touching any file.
|
|
For each proposed change, state the item name, the board, and the action:
|
|
</p>
|
|
<ul style="margin-top:0.5rem;padding-left:1.25rem;line-height:1.8">
|
|
<li><strong>Move to Done</strong> — task or bug that was completed this session</li>
|
|
<li><strong>Move to In Progress</strong> — task that was started but not finished</li>
|
|
<li><strong>Move to To Do</strong> — new task worth adding now</li>
|
|
<li><strong>Remove</strong> — item that is no longer relevant</li>
|
|
<li><strong>Add to Backlog</strong> — idea or future work surfaced during the session</li>
|
|
</ul>
|
|
<p style="margin-top:0.75rem">
|
|
Also note whether <strong>Update Outline</strong> should be run — recommend it
|
|
when new systems, subsystems, or conventions were added that the outline does not
|
|
yet describe.
|
|
</p>
|
|
<p style="margin-top:0.75rem">Wait for the user to confirm before continuing.</p>
|
|
</div>
|
|
|
|
<div class="card">
|
|
<h3>Step 3 — Apply the changes</h3>
|
|
<p>
|
|
After the user approves the proposal, edit the board HTML files accordingly.
|
|
Use the correct colour class for each lane:
|
|
</p>
|
|
<ul style="margin-top:0.5rem;padding-left:1.25rem;line-height:1.8">
|
|
<li><code>class="green hide-content"</code> — Done (Tasks)</li>
|
|
<li><code>class="red hide-content"</code> — Critical (Bugs)</li>
|
|
<li><code>class="yellow hide-content"</code> — In Progress (Tasks) or Visual/UI/UX (Bugs)</li>
|
|
<li><code>class="blue hide-content"</code> — To Do (Tasks) or MVP (Backlog)</li>
|
|
<li><code>class="purple hide-content"</code> — Nice To Have (Backlog)</li>
|
|
<li><code>class="orange hide-content"</code> — To The Moon (Backlog)</li>
|
|
</ul>
|
|
<p style="margin-top:0.75rem">
|
|
Keep the Done lane in Tasks focused — if it grows beyond three or four items,
|
|
ask the user whether old Done items should be cleared out.
|
|
</p>
|
|
</div>
|
|
|
|
</section>
|
|
|
|
<footer>
|
|
Roject — update board
|
|
</footer>
|
|
|
|
</div>
|
|
<script>var NAV_ROOT = '../../';</script>
|
|
<script src="../../_assets_/nav-data.js"></script>
|
|
<script src="../../_assets_/nav.js"></script>
|
|
</body>
|
|
</html>
|