251148c3ff
## Summary - add repository-wide quality tooling and verification scaffolding, including CI workflows, pnpm workspace setup, ESLint/Prettier/markdown checks, and generated-output verification helpers - reorganize skill sources and generation flow by introducing canonical `_source` variants, generator/manifests, reusable helper abstractions, and shared web-automation/browser utilities - clean up and expand documentation so the root README flows into docs and skill docs, with clearer development, reviewer, installer, and workflow guidance ## Notable changes - docs flow and consistency cleanup across `README.md`, `docs/README.md`, and related docs - new scripts for `check`, docs verification, generated-file verification, shell portability, and safe directory replacement - refactors in Atlassian and web-automation skill runtimes to reduce duplication and centralize reusable code - changelog, development documentation, and CI surface updates ## Test Plan - [ ] `pnpm run check` - [ ] review generated/manifests and skill sync outputs - [ ] smoke-check docs flow from `README.md` to `docs/README.md` to skill docs ## Notes - this branch currently includes tracked `skills/web-automation/shared/node_modules` content that should be reviewed carefully as potentially noisy/accidental committed artifacts Co-authored-by: Stefano Fiorini <stefano.fiorini@firsthorizon.com> Reviewed-on: #1
73 lines
1.7 KiB
Markdown
73 lines
1.7 KiB
Markdown
<!-- ⚠️ GENERATED FILE – do not edit directly. Edit the canonical source in skills/create-plan/_source/pi/ and run `pnpm run sync:pi`. -->
|
||
# Story Tracker: [Plan Title]
|
||
|
||
## Progress Summary
|
||
|
||
- **Current Milestone:** M1
|
||
- **Stories Complete:** 0/N
|
||
- **Milestones Approved:** 0/M
|
||
- **Last Updated:** YYYY-MM-DD
|
||
|
||
---
|
||
|
||
## Milestones
|
||
|
||
### M1: [Name]
|
||
|
||
| Story | Description | Status | Notes |
|
||
|-------|-------------|--------|-------|
|
||
| S-101 | [Brief description] | pending | |
|
||
| S-102 | [Brief description] | pending | |
|
||
| S-103 | [Brief description] | pending | |
|
||
|
||
**Approval Status:** pending
|
||
|
||
---
|
||
|
||
### M2: [Name]
|
||
|
||
| Story | Description | Status | Notes |
|
||
|-------|-------------|--------|-------|
|
||
| S-201 | [Brief description] | pending | |
|
||
| S-202 | [Brief description] | pending | |
|
||
| S-203 | [Brief description] | pending | |
|
||
|
||
**Approval Status:** pending
|
||
|
||
---
|
||
|
||
## Status Legend
|
||
|
||
| Status | Meaning |
|
||
|--------|---------|
|
||
| `pending` | Not started |
|
||
| `in-dev` | Currently being worked on |
|
||
| `completed` | Done - include commit hash in Notes |
|
||
| `deferred` | Postponed - include reason in Notes |
|
||
|
||
## Update Instructions (MANDATORY)
|
||
|
||
Before starting any story:
|
||
|
||
1. Mark story as `in-dev`
|
||
2. Update "Last Updated"
|
||
|
||
After completing any story:
|
||
|
||
1. Mark story as `completed`
|
||
2. Add local commit hash to Notes
|
||
3. Update "Stories Complete" and "Last Updated"
|
||
|
||
At milestone boundary:
|
||
|
||
1. Run lint/typecheck/tests for changed files
|
||
2. Commit (no push)
|
||
3. Request feedback
|
||
4. Apply feedback, re-check changed files, commit again
|
||
5. Mark milestone **Approval Status: approved** only after user confirms
|
||
6. Continue only after approval
|
||
|
||
After all milestones approved:
|
||
|
||
- Ask permission to push and then mark plan completed.
|