docs-update
1
总安装量
1
周安装量
#45829
全站排名
安装命令
npx skills add https://github.com/duc01226/easyplatform --skill docs-update
Agent 安装分布
antigravity
1
gemini-cli
1
Skill 文档
Phase 1: Parallel Codebase Scouting
You (main agent) must spawn scouts – subagents cannot spawn subagents.
- Run
ls -lato identify actual project directories - Spawn 2-4
scout-external(preferred, uses Gemini 2M context) orscout(fallback) via Task tool - Target directories that actually exist – adapt to project structure, don’t hardcode paths
- Merge scout results into context summary
Phase 2: Documentation Update (docs-manager Agent)
Pass the gathered file list to docs-manager agent to update documentation:
README.md: Update README (keep it under 300 lines)docs/project-overview-pdr.md: Update project overview and PDR (Product Development Requirements)docs/codebase-summary.md: Update codebase summarydocs/code-standards.md: Update codebase structure and code standardsdocs/system-architecture.md: Update system architecturedocs/project-roadmap.md: Update project roadmapdocs/deployment-guide.md[optional]: Update deployment guidedocs/design-guidelines.md[optional]: Update design guidelines
Additional requests
<additional_requests> $ARGUMENTS </additional_requests>
[CRITICAL] Code Evidence Requirements
All documentation MUST follow evidence rules from .claude/skills/feature-docs/SKILL.md â [CRITICAL] MANDATORY CODE EVIDENCE RULE
Quick Reference
- Format:
**Evidence**: {FilePath}:{LineNumber} - Status: â Verified / â ï¸ Stale / â Missing
- Verification: 3-pass verification required before completion
Stale Evidence Detection
When updating documentation:
- Read actual source files at claimed line numbers
- Verify evidence matches documented behavior
- Update stale references – mark with â ï¸ if line numbers changed
- Refresh line numbers after code changes
Evidence Verification Table (Required)
| Entity/Component | Documented Lines | Actual Lines | Status |
|---|---|---|---|
Entity.cs |
L6-15 | L6-15 | â Verified |
Handler.cs |
L45-60 | L52-67 | â ï¸ Stale |
Important
- Use
docs/directory as the source of truth for documentation.
IMPORTANT: Do not start implementing.
IMPORTANT Task Planning Notes
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed