Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odooWrote 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/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-feature-create)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-feature-create"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-feature-create.svg" alt="Measured on agentmods" 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.00000 | $0.00935 |
| Opus 5 | $0.00000 | $0.00467 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
odoo-feature-create 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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-feature-create - Create Odoo Feature Specification
Create comprehensive feature specifications for Odoo modules with ERP-specific considerations and implementation patterns.
Usage
/odoo-feature-create [module-name]-[feature-name] "Feature description"
Examples
/odoo-feature-create hr-attendance-tracking "Employee attendance tracking system"
/odoo-feature-create inventory-advanced-routing "Advanced warehouse routing with multi-step operations"
/odoo-feature-create sales-commission-calculator "Automated sales commission calculation system"
What This Command Does
This command creates detailed feature specifications for Odoo modules including:
- Business Process Analysis: ERP workflow integration
- Technical Architecture: Odoo-specific implementation patterns
- User Experience Design: Forms, views, and user interactions
- Integration Planning: API endpoints and external system connections
- Testing Strategy: Comprehensive testing approach for ERP features
Instructions
Use the @odoo-spec-task-executor agent to create Odoo feature specifications:
Create a comprehensive Odoo feature specification using odoo-requirements-template.md, odoo-design-template.md, and odoo-tasks-template.md:
# Feature Specification Structure
## 1. Business Requirements Analysis
- **ERP Context**: How this feature fits into existing Odoo workflows
- **User Stories**: From different ERP user perspectives (Admin, User, Accountant, etc.)
- **Business Rules**: ERP-specific validation and business logic
- **Multi-Company Impact**: How feature behaves in multi-company environments
- **Localization Requirements**: Country-specific adaptations needed
## 2. Technical Design
- **Module Structure**: Following Odoo conventions
- **Model Design**:
- Field definitions with proper Odoo field types
- Compute methods and onchange triggers
- Constraints and validation rules
- Inheritance patterns (_inherit/_inherits)
- **View Architecture**:
- Form views with proper widget selection
- Tree views with appropriate filters and search
- Kanban views for visual workflow management
- Dashboard and reporting integration
- **Security Framework**:
- Access rights (ir.model.access.csv)
- Record rules for data filtering
- Groups and permissions structure
## 3. Integration Points
- **Core Modules**: Integration with existing Odoo modules
- **External APIs**: Third-party system connections
- **Webhooks**: Real-time data synchronization
- **Scheduled Actions**: Background processing requirements
## 4. User Experience
- **Navigation**: Menu structure and placement
- **Workflow**: Step-by-step user journey
- **Forms and Views**: User-friendly interface design
- **Reports**: PDF generation and dashboard analytics
- **Mobile Support**: Mobile app compatibility
## 5. Implementation Plan
- **Phase 1**: Core functionality development
- **Phase 2**: Integration and testing
- **Phase 3**: UI/UX refinement
- **Phase 4**: Performance optimization and deployment
## 6. Testing Strategy
- **Unit Tests**: Model method validation
- **Integration Tests**: Cross-module workflow testing
- **UI Tests**: Tour scripts for user interface
- **Performance Tests**: Load testing for critical operations
- **Data Migration Tests**: Upgrade path validation
Generate implementation tasks following Odoo development best practices.
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.
- 8d ago First seen · 115 lines · 0 tokens per session scan A 774593268f59
odoo-feature-create is a command published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 935 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.