chore(docs): remove false-positive TODOs from example documentation

[sjnims]

Summary

Removes TODO: prefixes from example documentation to prevent the weekly maintenance workflow from flagging them as action items.

Problem

Fixes #51

The weekly maintenance report flagged 3 TODOs in documentation-patterns.md, but these were actually part of an example command specification template showing what a "FUTURE IMPROVEMENTS" section might look like—not real action items for the codebase.

Solution

Removed the TODO: prefixes while preserving the FUTURE IMPROVEMENTS section content. This maintains the documentation's purpose (showing a pattern) without triggering false positives in maintenance scans.

Alternatives Considered

1. Create issues for the features - Not appropriate since these are hypothetical examples, not planned features
2. Exclude the file from TODO scanning - Would be overly broad and might miss real TODOs
3. Change to "Planned:" prefix - Simpler to just remove the prefix entirely

Changes

• plugins/plugin-dev/skills/command-development/references/documentation-patterns.md: Removed TODO: prefixes from 3 example items

Testing

• Verified no TODOs remain in the file
• Linting passes

---

🤖 Generated with Claude Code

[claude]

Claude finished @sjnims's task —— View job

---

PR Review: chore(docs): remove false-positive TODOs

Summary: ✅ Looks good - ready to merge

What's Good

1. Problem clearly identified and solved: The PR correctly addresses issue Weekly Maintenance Report - 2025-12-08 #51 by removing TODO: prefixes from example documentation that were triggering false positives in the weekly maintenance workflow.

2. Minimal, surgical change: The fix is precisely targeted - only 3 lines changed, removing the TODO: prefix while preserving the actual content. This maintains the documentation's purpose (showing a pattern) without triggering automated scans.

3. Context preserved: The FUTURE IMPROVEMENTS: section header remains intact, making it clear these are still example improvement items, just without the TODO: keyword that would trigger scanning tools.

4. Clean commit history: Single focused commit with clear message explaining the "why" behind the change.

5. Markdown linting: ✅ File passes markdownlint with no issues.

Verification

• ✅ Changed file: plugins/plugin-dev/skills/command-development/references/documentation-patterns.md (lines 590-592)
• ✅ Changes are in a references/ documentation file (appropriate location)
• ✅ No markdown lint violations
• ✅ Content remains clear and useful as an example pattern
• ✅ No other TODOs introduced

Checklist Verification

According to the PR description:

• ✅ Verified no TODOs remain in the file
• ✅ Linting passes (confirmed by markdownlint)

Notes

The approach taken (removing the prefix entirely) is cleaner than the alternatives considered:

• Creating issues for hypothetical examples would clutter the backlog
• Excluding the file would be too broad
• Changing to "Planned:" would still be unnecessary keyword noise

This is a good example of balancing documentation clarity with tooling requirements.

---

Recommendation: Approve and merge. This is a straightforward documentation fix that solves the false-positive issue without compromising the quality or clarity of the example.