**Planning Structure:** - TODO.md - Sprint planning and current tasks - ROADMAP.md - Long-term vision and milestones - .github/ISSUE_TEMPLATE/ - Issue templates for features and MCP tools **TODO.md:** - 5 phases: Core (done), Enhancement, Advanced, Docs, Integrations - Current sprint tasks clearly defined - Progress tracking with checkboxes **ROADMAP.md:** - Vision and milestones - v1.0 (done), v1.1 (in progress), v1.2-3.0 (planned) - Feature ideas categorized by priority - Metrics and goals - Release schedule **Issue Templates:** - feature_request.md - General features - mcp_tool.md - New MCP tools specifically Next: Fix tests, test MCP with Claude Code, document setup 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
43 lines
853 B
Markdown
43 lines
853 B
Markdown
---
|
|
name: MCP Tool Request
|
|
about: Suggest a new tool for the MCP server
|
|
title: '[MCP] Add tool: '
|
|
labels: mcp, enhancement
|
|
assignees: ''
|
|
---
|
|
|
|
## Tool Name
|
|
<!-- e.g., auto_detect_selectors -->
|
|
|
|
## Tool Description
|
|
<!-- What does this tool do? -->
|
|
|
|
## Input Parameters
|
|
```json
|
|
{
|
|
"param1": {
|
|
"type": "string",
|
|
"description": "...",
|
|
"required": true
|
|
}
|
|
}
|
|
```
|
|
|
|
## Expected Output
|
|
<!-- What should the tool return? -->
|
|
|
|
## Use Case Example
|
|
<!-- How would users interact with this tool? -->
|
|
```
|
|
User: "Auto-detect selectors for https://docs.example.com"
|
|
Tool: Analyzes page structure and suggests optimal selectors
|
|
```
|
|
|
|
## CLI Integration
|
|
<!-- Which CLI tool does this wrap? Or is it new logic? -->
|
|
- [ ] Wraps existing CLI tool: `cli/tool_name.py`
|
|
- [ ] New functionality
|
|
|
|
## Implementation Notes
|
|
<!-- Technical details, dependencies, etc. -->
|