From 1ecc7bc76f3cbc4323887eb881e8ee03e5c7770c Mon Sep 17 00:00:00 2001 From: nathan Date: Fri, 3 Apr 2026 12:02:17 -0400 Subject: [PATCH] Added formalized LLM prompt for consistant README updates. --- .github/prompts/update-readme.prompt.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .github/prompts/update-readme.prompt.md diff --git a/.github/prompts/update-readme.prompt.md b/.github/prompts/update-readme.prompt.md new file mode 100644 index 0000000..2871e8f --- /dev/null +++ b/.github/prompts/update-readme.prompt.md @@ -0,0 +1,22 @@ +Act as a Senior Technical Program Manager. I need to update the `README.md` for my 'Workday-MCP' project to serve as a high-visibility Status Page. + +**CONTEXT:** +- We just moved from a single-file script to a modular architecture (`server.py` + `lib/data.py`). +- We have 3 operational tools: `get_worker_status`, `get_worker_manager`, and `scan_manager_mismatches`. +- Current Goal: WIS-017 (Manager Mismatch Detection) is prototyped and functional with 9 mock records. +- Next Milestone: WIS-008 (Transitioning from Mock to Real Workday API). + +**REQUIREMENTS:** +1. **Visual Status:** Use a "Traffic Light" system for project components: + - 🟢 Green: Functional/Production-Ready + - 🟡 Yellow: In Progress/Development + - 🔴 Red: Blocked/Not Started +2. **Standardization:** Ensure the README reflects our "Discipline Drives Quality" pillar (e.g., mention Type Hinting, Pylance-zero-error status, and modular structure). +3. **Sprint Alignment:** Reference the WIS (Workday Integration Suite) IDs to maintain traceability to our 2026 roadmap. +4. **Readability:** Use clean Markdown tables and bold headers for scannability. + +**INPUT DATA:** +[PASTE YOUR CURRENT README HERE] + +**RECENT ACTIVITY:** +[PASTE YOUR RECENT GIT LOG OR SUMMARY HERE] \ No newline at end of file