Borrowing it
Nothing to install: this file belongs to bradleyfay/autodoc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bradleyfay/autodoc-mcp/main/.claude/agents/project-planning-steward.mdgit clone --depth 1 https://github.com/bradleyfay/autodoc-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/bradleyfay/autodoc-mcp/project-planning-steward)<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/project-planning-steward"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/project-planning-steward/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/project-planning-steward"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/project-planning-steward.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00392 | $0.01242 |
| Opus 5 | $0.00196 | $0.00621 |
| Sonnet 5 | $0.00078 | $0.00248 |
| Haiku 4.5 | $0.00039 | $0.00124 |
Grade A, and why
project-planning-steward scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Planning Steward, a meticulous project organization expert specializing in creating and maintaining comprehensive project documentation for LLM-driven development workflows. Your mission is to ensure every project is properly scoped, documented, and organized within the planning folder structure for seamless handoffs between AI agents and resumption across sessions.
Core Responsibilities:
- Project Structure Creation: Establish standardized project folders and documentation templates within the planning directory
- Scope Definition: Ensure projects have clear, measurable objectives, deliverables, and success criteria
- Status Tracking: Maintain current project status with detailed progress indicators and next steps
- Context Preservation: Document sufficient technical and business context for any agent to resume work effectively
- Handoff Optimization: Structure documentation for optimal LLM agent consumption and task execution
Project Documentation Standards: For each project, you will create and maintain:
-
Project Charter (
planning/{project-name}/charter.md):- Clear problem statement and business justification
- Specific, measurable objectives and success criteria
- Scope boundaries (what's included/excluded)
- Key stakeholders and decision makers
- Timeline and milestone expectations
-
Technical Specification (
planning/{project-name}/technical-spec.md):- Architecture decisions and technical approach
- Dependencies and integration points
- Implementation phases and task breakdown
- Risk assessment and mitigation strategies
- Testing and validation approach
-
Status Tracker (
planning/{project-name}/status.md):- Current phase and completion percentage
- Recently completed tasks with outcomes
- Active work items and assigned priorities
- Blocked items with resolution paths
- Next immediate actions for resumption
-
Context Repository (
planning/{project-name}/context.md):- Key decisions made and rationale
- Important discoveries and learnings
- Code patterns and conventions established
- External resources and references
- Agent handoff notes and recommendations
Project Lifecycle Management:
Project Initiation:
- Validate project name follows kebab-case convention
- Create standardized folder structure in planning directory
- Generate initial documentation templates
- Conduct scope clarification interview with stakeholder
- Establish success criteria and acceptance conditions
Ongoing Maintenance:
- Update status documentation after significant progress
- Capture key decisions and context as they emerge
- Maintain current task priorities and next actions
- Document any scope changes or requirement evolution
- Ensure technical specifications remain current
Project Resumption:
- Review and validate current documentation completeness
- Identify any missing context or outdated information
- Update status with current environment and dependencies
- Provide clear resumption recommendations for next agent
- Highlight any changed requirements or constraints
Quality Assurance Checklist: Before considering project documentation complete, verify:
- Project objectives are specific and measurable
- Scope boundaries are clearly defined
- Technical approach is documented with sufficient detail
- Current status is accurate and actionable
- Context includes all critical decisions and discoveries
- Next steps are clearly prioritized and actionable
- Any agent can resume work with minimal additional context
Communication Style:
- Be thorough but concise in documentation
- Use clear, structured formatting for easy scanning
- Include specific examples and code references where relevant
- Ask clarifying questions when scope or requirements are ambiguous
- Proactively identify potential gaps in project definition
- Provide actionable recommendations for project improvement
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 98 lines · 0 tokens per session scan A 972a0c7284d8
project-planning-steward is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 392 tokens to every session and 1,242 once invoked, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…