senior-planner-agent

Audits and synchronizes eight project documentation files with code changes and sprint progress.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/pu-roi/LANES --skill senior-planner-agent-pu-roi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-planner-agent
Source: https://github.com/pu-roi/LANES/tree/main/.agents/skills/senior-planner-agent
Command: npx skills add https://github.com/pu-roi/LANES --skill senior-planner-agent-pu-roi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project documentation drifts out of sync with the codebase as features ship, bugs get fixed, and architectures evolve. This Skill keeps the LANES project's eight authoritative documentation files accurate, timestamped, and attributed to the correct developer after every code change. ## Core Features & Use Cases - Documentation Auditing: Reviews code changes and updates the tech stack, task plan, progress tracker, feature reference, decisions log, system documentation, database design plan, and bug log accordingly. - Sprint & Progress Tracking: Checks off completed milestones in the task plan and records delivered work in reverse chronological order in the progress tracker. - Author Attribution: Detects the active developer via git config and branch name, then tags new tasks, decisions, and bug entries with their GitHub identity. - Use Case: After merging a feature branch that adds a new API endpoint and fixes a routing bug, invoke this Skill to update the system documentation, log the bug resolution with root cause analysis, and mark the sprint task complete. ## Quick Start Ask the agent to audit the latest code changes and update all affected project documentation files with proper timestamps and author attribution.

Frequently Asked Questions about senior-planner-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep project documentation in sync with code changes?▼

Use this Skill to audit code changes and update the relevant documentation files automatically. It covers tech stack, task plans, progress tracking, feature references, architectural decisions, system documentation, database design, and bug logs.

How do I track sprint progress across multiple developers?▼

The Skill checks off completed tasks in the task plan and records delivered milestones in the progress tracker in reverse chronological order. It detects the active developer via git config and branch name to attribute each entry correctly.

What qualifies as a feature worth documenting in a feature reference?▼

Only standalone major platform capabilities qualify, such as core domain engines or primary system pillars. Routine sub-features, UI tweaks, bug fixes, and refactors are excluded and belong in the progress log or system documentation instead.

How should bug fixes be documented in a project bug log?▼

Each bug entry records status, severity, and resolver identity, plus a problem description, root cause analysis, solution strategy, and the exact files modified. Entries are added whenever a bug is investigated, in progress, or resolved.

When should architectural decisions be logged?▼

Log only major architectural pivots, framework replacements, security model changes, or fundamental paradigm shifts in the decisions file. Routine sprint progress, minor refactors, and bug fixes should never be added there.