AGENTS.md

Guidance for coding agents working on LMSSEP Planning MCP Server.

Project Overview

The planning server provides project planning and WBS execution tools. It can initialize a planning session, ask follow-up questions, finalize a plan, parse a Markdown WBS, mark tasks complete, report status, list executable next tasks, and generate execution reports.

Key paths:

• planning/README.md: feature and example documentation.
• planning/main.py: MCP entrypoint.
• planning/requirements.txt: dependencies.
• planning/configs/: local planning configuration.
• output/planning/: generated plans and WBS reports.

Setup Commands

bashcd <project-root>/planning
pip install -r requirements.txt
python3 main.py

Use placeholders such as <PROJECT_DESCRIPTION>, <SESSION_ID>, <TASK_ID>, and <WBS_MARKDOWN> in examples.

Planning Rules

• Initialize with a concrete project description.
• Ask for missing scope, timeline, owners, constraints, and risks before finalizing.
• Final plans should include milestones, WBS, timeline, resource assumptions, and risks.
• Do not invent user approval, budget, or dependency facts.

WBS Rules

• Keep Markdown hierarchy stable so parsing remains deterministic.
• Task IDs returned by parsing are the source of truth for execution updates.
• Only mark a task complete when notes or evidence support completion.
• Report blockers explicitly; do not skip blocked tasks silently.

Testing

• Test WBS parsing with nested headings, bullets, empty sections, and malformed input.
• Test task state transitions and next-task calculation.
• Verify report generation after partial completion and after blocked tasks.

Security

• Plans can contain business-sensitive schedules and staffing assumptions. Keep generated outputs local unless publication is intended.
• Redact internal project names, owner identities, and dates in public examples when needed.