NINI
29 lines
927 B
Markdown
29 lines
927 B
Markdown
---
|
|
description: Summarize the current FESA project status and next work from PLAN.md and PROGRESS.md.
|
|
---
|
|
|
|
# /status
|
|
|
|
## Preflight
|
|
|
|
- Read `/AGENTS.md`, `/PROGRESS.md`, `/PLAN.md`, and `/docs/README.md`.
|
|
- Check whether the user asked for status only or also wants edits.
|
|
- Do not modify files unless the user explicitly asks for synchronization or cleanup.
|
|
|
|
## Task
|
|
|
|
- Summarize current project status, blockers, risks, and the next actionable items.
|
|
- Mention whether solver implementation has started.
|
|
- Highlight unresolved Phase 1 readiness items and the current validation state.
|
|
|
|
## Verification
|
|
|
|
- If no edits were made, state that no validation command was required.
|
|
- If the user asked you to update files, run `python scripts/validate_workspace.py`.
|
|
|
|
## Result
|
|
|
|
- **Action**: reported FESA status
|
|
- **Status**: success | partial | blocked
|
|
- **Details**: current objective, blockers, next tasks, and validation note
|