sitemap-task-bias

$npx mdskill add agentlas-ai/Agentlas-OS/sitemap-task-bias

Audits agent-team sitemaps and task bias coverage.

  • Ensures no important concept or surface is missed in planning.
  • Depends on sitemap, validation ledger, and concept coverage lists.
  • Compares request against required concept coverage and adds task biases.
  • Returns covered, missing, task_biases, and evidence_files.

SKILL.md

.github/skills/sitemap-task-biasView on GitHub ↗
---
name: sitemap-task-bias
description: "Use when creating or auditing an agent-team sitemap, Task Bias ledger, concept coverage, product surface map, validation chain, or missing-concept check."
---

# Sitemap Task Bias

## Procedure

1. List the user-facing surfaces, workflows, agent roles, skills, memory scopes,
   runtime adapters, policy gates, and verification lanes.
2. Compare the request against required concept coverage:
   - sitemap;
   - PM Soul;
   - memory architecture;
   - all-LLM runtime architecture;
   - public/private boundary;
   - install and verification path.
3. Add task biases that protect the build from dropping important concerns.
4. Record skipped or blocked concepts in `.agentlas/validation-ledger.jsonl`.

## Output

Return `covered`, `missing`, `task_biases`, and `evidence_files`.

More from agentlas-ai/Agentlas-OS

SkillDescription
agent-team-designUse when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
agentlas-auto-activationUse when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
agentlas-core-engine-meta-agentUse when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
agentlas-packagingUse when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.
agentlas-security-scanUse when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret `hephaestus security scan`.
clarify-question-loopUse when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
hephaestus-buildUse when the user types /prompts:hep-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.
hephaestus-cloudUse when the user types /hep-cloud or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.
hephaestus-networkUse when the user types /hep-network, mentions @Hephaestus, or asks Agentlas to staff a task from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM is the temporary orchestrator.
hephaestus-stormUse when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.