[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TP1PJMYDN0S18HGST6NGD":3,"skill-same:01M75TP1PJMYDN0S18HGST6NGD":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M75TP1PJMYDN0S18HGST6NGD","odoo-design-doc",null,"Write an Odoo solution or technical design document, discovering current state via read-only Odoo tools first. Use to design or spec an Odoo feature, module, or customization: models, fields, views, security, migration, upgrade impact, rollout.","Crpaxton4\u002Fdevcontainer-features","Crpaxton4","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10190720?v=4","01M75TNGAF4N2K56AS0WDN38AM","Chris Paxton","01M75TNGB1E99BTJEGPXPQDRAB",0,"MIT","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-design-doc\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: odoo-design-doc\ndescription: \"Write an Odoo solution or technical design document, discovering current state via read-only Odoo tools first. Use to design or spec an Odoo feature, module, or customization: models, fields, views, security, migration, upgrade impact, rollout.\"\nuser-invocable: false\n---\n# Odoo solution design document\n\nA technical design an Odoo developer can build from and a client can approve. Write it\nonly when the request asks for a design document. Every tool below is read-only.\n\n## 1. Discover current state first\n\n- `search_projects(query=...)` then `get_task(task_id=\u003Cid>, include=[\"description\",\n  \"chatter\", \"dependencies\"])` → the requirement and the decisions behind it.\n- `search_chatter(query=\"\u003Cmodel or feature>\", model=\"project.task\")` → prior\n  decisions, rejected approaches, constraints.\n- `get_task_attachments(task_id=\u003Cid>)` then\n  `read_attachment(attachment_id=\u003Cid>, mode=\"text\")` → existing specs, ERDs, mockups.\n- `search_knowledge_articles(query=...)` then `read_knowledge_article(article_id=\u003Cid>)`\n  → architecture notes and conventions (Enterprise only; skip on error).\n\nRecord the target Odoo version and edition first. They decide which APIs are valid and\nwhether Enterprise models exist.\n\n## 2. Template\n\nFill each section. Use real technical names everywhere: model `model.name`, field\n`field_name`, XML ids. Mark a name you propose as *proposed*.\n\n### Overview\n- Problem statement, goal and success criteria, one paragraph.\n- In scope and out of scope.\n\n### Data model\n- Model: `technical.model.name`, new or extended through `_inherit`.\n- Fields table: technical name · type · required · default · compute or related (with\n  `@api.depends`) · help. Mark `store=True` where a computed field is searched or grouped.\n- Relationships and `ondelete` behaviour for Many2one fields.\n\n### Views and UX\n- Views to add or extend: form, list, search, kanban, pivot, graph.\n- Menu items and window actions, with the model and the view mode.\n- For an extension, the inherited view and the `xpath` and `position`.\n\n### Business logic\n- Methods and their triggers: button, `@api.model`, automation, cron.\n- Computed and related fields, `@api.constrains`, `@api.onchange`.\n- Automated or server action against code: state which and why.\n\n### Security\n- Access rights (`ir.model.access.csv`): per group, the read\u002Fwrite\u002Fcreate\u002Funlink matrix.\n- Record rules (`ir.rule`): domain, groups, global or group-specific, multi-company.\n- New security groups and their inheritance.\n\n### Data migration\n- What existing data moves or is backfilled, and its source.\n- Approach: pre\u002Fpost migration scripts, `noupdate` data, or a one-off script.\n- Idempotency and recovery from a partial run.\n\n### Upgrade impact\n- Version-specific APIs used and deprecations on the target version.\n- Impact on existing customizations and third-party modules.\n- Whether the design survives the client's next planned upgrade.\n\n### Rollout plan\n- Environments: dev → staging\u002FUAT → production.\n- Steps: module install or upgrade, data load, config, smoke test.\n- Rollback plan per risky step: backup point, reverse migration.\n- UAT owner and go\u002Fno-go criteria.\n\n### Open questions\n- Every unresolved decision, with who must answer it.\n\n## Stop conditions\n\n- Never invent a technical name that can already exist. Derive it from the records.\n- Never skip security. A design without access rights and record rules is incomplete.\n- Never use an API without the version it requires or was removed in.\n- Never present the design as final while open questions remain. List them.\n","# Odoo solution design document\n\nA technical design an Odoo developer can build from and a client can approve. Write it\nonly when the request asks for a design document. Every tool below is read-only.\n\n## 1. Discover current state first\n\n- `search_projects(query=...)` then `get_task(task_id=\u003Cid>, include=[\"description\",\n  \"chatter\", \"dependencies\"])` → the requirement and the decisions behind it.\n- `search_chatter(query=\"\u003Cmodel or feature>\", model=\"project.task\")` → prior\n  decisions, rejected approaches, constraints.\n- `get_task_attachments(task_id=\u003Cid>)` then\n  `read_attachment(attachment_id=\u003Cid>, mode=\"text\")` → existing specs, ERDs, mockups.\n- `search_knowledge_articles(query=...)` then `read_knowledge_article(article_id=\u003Cid>)`\n  → architecture notes and conventions (Enterprise only; skip on error).\n\nRecord the target Odoo version and edition first. They decide which APIs are valid and\nwhether Enterprise models exist.\n\n## 2. Template\n\nFill each section. Use real technical names everywhere: model `model.name`, field\n`field_name`, XML ids. Mark a name you propose as *proposed*.\n\n### Overview\n- Problem statement, goal and success criteria, one paragraph.\n- In scope and out of scope.\n\n### Data model\n- Model: `technical.model.name`, new or extended through `_inherit`.\n- Fields table: technical name · type · required · default · compute or related (with\n  `@api.depends`) · help. Mark `store=True` where a computed field is searched or grouped.\n- Relationships and `ondelete` behaviour for Many2one fields.\n\n### Views and UX\n- Views to add or extend: form, list, search, kanban, pivot, graph.\n- Menu items and window actions, with the model and the view mode.\n- For an extension, the inherited view and the `xpath` and `position`.\n\n### Business logic\n- Methods and their triggers: button, `@api.model`, automation, cron.\n- Computed and related fields, `@api.constrains`, `@api.onchange`.\n- Automated or server action against code: state which and why.\n\n### Security\n- Access rights (`ir.model.access.csv`): per group, the read\u002Fwrite\u002Fcreate\u002Funlink matrix.\n- Record rules (`ir.rule`): domain, groups, global or group-specific, multi-company.\n- New security groups and their inheritance.\n\n### Data migration\n- What existing data moves or is backfilled, and its source.\n- Approach: pre\u002Fpost migration scripts, `noupdate` data, or a one-off script.\n- Idempotency and recovery from a partial run.\n\n### Upgrade impact\n- Version-specific APIs used and deprecations on the target version.\n- Impact on existing customizations and third-party modules.\n- Whether the design survives the client's next planned upgrade.\n\n### Rollout plan\n- Environments: dev → staging\u002FUAT → production.\n- Steps: module install or upgrade, data load, config, smoke test.\n- Rollback plan per risky step: backup point, reverse migration.\n- UAT owner and go\u002Fno-go criteria.\n\n### Open questions\n- Every unresolved decision, with who must answer it.\n\n## Stop conditions\n\n- Never invent a technical name that can already exist. Derive it from the records.\n- Never skip security. A design without access rights and record rules is incomplete.\n- Never use an API without the version it requires or was removed in.\n- Never present the design as final while open questions remain. List them.\n",{"name":5,"description":7,"user-invocable":20},"main","043a283d6e259355cd1601e000c45e1ee8ebd8bd","plugins\u002Fodoo-dev\u002Fskills\u002Fodoo-design-doc","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features","https:\u002F\u002Fgithub.com\u002FCrpaxton4","Computer Science\r\nMiami University","2026-11-02 22:38:24",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Crpaxton4\u002Fdevcontainer-features --skill odoo-design-doc",{"tool":37,"command":38},"bunx","bunx skills add Crpaxton4\u002Fdevcontainer-features --skill odoo-design-doc",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Crpaxton4\u002Fdevcontainer-features --skill odoo-design-doc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-design-doc\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75TQ56QVZX3Q680X89RT6FT","report-incident","Draft a terse GitHub issue for an incident in the Odoo dev suite (odoo-dev, odoo-orchestrator, dispatcher), with a current environment block and no private data. Files it only after you approve. Use when a tool or workflow failed.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-orchestrator\u002Fskills\u002Freport-incident\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75TQ2RBNTA4EXJ4BQ3HRYXY","principles","Engineering principles indexed as one-liners: safety and correctness, design and architecture, composition and interfaces, code structure, performance, visibility. Use when writing new code, reviewing a diff, or justifying a design choice.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75TQ0DVV793EWKKFN26408W","odoo-upgrade","Plan and run code upgrades of custom Odoo modules between major versions (16.0→17.0→18.0→19.0). Use to migrate or port a module or addon, for breaking changes, a module inventory, or an upgrade estimate or plan.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-upgrade\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75TPXTR66V72DA42QSDQDPM","odoo-upgrade-project","Human SOP for a whole Odoo upgrade project past the code port: staging database upgrade through upgrade.odoo.com, on-prem restore, cutover, go-live, support tickets and functional requirements. A planning reference.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-upgrade-project\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75TPVQ93TAY7KDB6XYDTVMK","odoo-test-run","Run an Odoo module's unit tests and HttpCase browser tours on a throwaway database and return machine-checkable evidence: tests executed, tours executed, failure lines. Use before a PR, after a fix, or when a green run never said how many tests ran.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-test-run\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75TPR5N29G38HDSCKYEC350","odoo-task-env","Stand up the working environment for one Odoo task: find work that already exists, create or reuse an isolated git worktree on the task branch, bring a runnable stack up. Use at the START of implementing any task, and whenever one is picked back up.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-task-env\u002FSKILL.md",[],[]]