43 lines
1.6 KiB
Markdown
43 lines
1.6 KiB
Markdown
---
|
|
id: TASK-10
|
|
title: Build the local skills registry
|
|
status: To Do
|
|
assignee: []
|
|
created_date: '2026-06-03 19:13'
|
|
labels:
|
|
- mvp
|
|
- agent
|
|
- skills
|
|
dependencies:
|
|
- TASK-2
|
|
references:
|
|
- PRD.md
|
|
priority: high
|
|
ordinal: 10000
|
|
---
|
|
|
|
## Description
|
|
|
|
<!-- SECTION:DESCRIPTION:BEGIN -->
|
|
Create the local skills registry concept for the agent. Design and marketing skills are stored in the project repository and summarized in a skills.md registry so the agent can select relevant analysis and writing guidance for each audit while the dashboard shows which skills were used.
|
|
<!-- SECTION:DESCRIPTION:END -->
|
|
|
|
## Acceptance Criteria
|
|
<!-- AC:BEGIN -->
|
|
- [ ] #1 A project-local skills directory or convention exists for imported design and marketing skills
|
|
- [ ] #2 skills.md lists each skill with name, purpose, when to use, when not to use, required input, expected output, and category
|
|
- [ ] #3 Agent code can load and parse the skills registry into structured skill metadata
|
|
- [ ] #4 Audit records store the list of used skills, including skill name/category and version or source where available
|
|
- [ ] #5 Dashboard audit detail shows a compact Verwendete Skills overview, but public audit pages do not
|
|
<!-- AC:END -->
|
|
|
|
## Implementation Plan
|
|
|
|
<!-- SECTION:PLAN:BEGIN -->
|
|
1. Define project-local skill storage conventions.
|
|
2. Create the initial skills.md registry format and seed entries for design, UX, marketing, copy, SEO, and offer-writing skills.
|
|
3. Add parser/loader for registry metadata.
|
|
4. Store selected skill metadata with each audit.
|
|
5. Show used skills in the internal audit detail UI only.
|
|
<!-- SECTION:PLAN:END -->
|