Product Skills
Product skills teach Codex how to reason about Anuva product concepts and cross-repository architecture. They are not primarily coding procedures; they package product context, invariants, decision questions, and planning outputs.
flowchart TD
idea["Product or architecture idea"] --> productSkill["Product skill"]
productSkill --> context["Product context"]
productSkill --> invariants["Design invariants"]
productSkill --> questions["Decision questions"]
productSkill --> output["Brief, decision record, or repository impact"]Product Skill Goals
Product skills should help Codex:
- reason consistently about Anuva concepts
- identify affected capabilities
- produce better architecture questions
- avoid premature implementation
- create cross-repository plans
- preserve product decisions as reusable context
Candidate Product Skills
| Skill | Purpose | Primary Output |
|---|---|---|
architecture-review |
Evaluate a proposed change against Anuva architecture. | Architecture review or decision record |
capability-mapping |
Map a request to capabilities and owning repositories. | Capability impact table |
cross-repository-feature |
Plan feature work spanning multiple repositories. | Feature brief and repository impact |
repository-extraction |
Evaluate when a capability should become a separate repository. | Extraction decision and migration plan |
product-brief |
Turn raw product ideas into structured implementation context. | Product brief |
docs-portal-planning |
Decide how knowledge should appear in the published portal. | Publishing plan |
Product Versus Engineering Skills
| Product Skill | Engineering Skill |
|---|---|
| Helps decide what should happen. | Helps perform the work. |
| Produces briefs, decisions, and impact maps. | Produces patches, tests, docs, and logs. |
| Starts from product or architecture context. | Starts from a scoped task. |
| Often runs in the handbook. | Often runs in an implementation repository. |
Product Skill Output Pattern
Product skills should usually produce:
- summary
- relevant capabilities
- affected repositories
- assumptions
- non-goals
- open questions
- repository impact
- docs impact
- acceptance criteria
Guardrail
Product skills should not invent repository implementation details. They should identify what each repository must determine locally.