norrisaftcc / norrisaftcc/algorithm-liza
Persona source format and the compile step
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
A single authored source per persona — Markdown with YAML frontmatter carrying name, description, model, tags and a budget token ceiling — compiled into a Claude Code subagent file and, where relevant, a compact variant for LIZA.
Needs a build command and a CI check that compiled outputs are current, otherwise the two copies drift and the source stops being authoritative.
Blocked on M2: there is no point defining a token budget for a system prompt LIZA does not yet have. Rationale in ADR-0004.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading ADR-0004 and confirm the M2 dependency, then map the authored Markdown/YAML persona source to the Claude Code subagent output and the compact LIZA variant. Define the build command and CI freshness check so compiled outputs remain current and the source stays authoritative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, yaml
- Domain
- build-system, ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100