workspace-management

Quick-adds a piece of information to workspace memory without interrupting workflow. Infers memory type and scope from content, requires at most 1 question. Use for rapid memory capture during development.

Validates all context files in workspace/context/ for integrity issues including frontmatter completeness, broken wikilinks, alias uniqueness, and bidirectional relationships. Offers per-finding fix or dismiss. Use when verifying context entity health.

Audits local issue files by spawning specialized auditor agents that leave feedback markers, then validates findings and discusses resolution with the user. Use when reviewing created issues for quality, completeness, and adherence to project standards before implementation.

Validates spec completeness and hierarchy integrity by scanning workspace/specs/ for missing relationships, orphaned entities, broken wikilinks, and incomplete frontmatter. Use when reviewing spec quality or verifying hierarchy consistency.

Validates entire workspace integrity across all directories by running 6 validation phases — wikilink resolution, orphan detection, frontmatter validation, hierarchy validation, alias uniqueness, and template compliance. Use when performing a full workspace health check.

Audits issue files for architectural gaps, ambiguities, contradictions, convention divergence, bad patterns, and design principle violations. Use when reviewing issue specifications for architectural completeness before implementation.

Reviews implemented code for architectural gaps, convention divergence, bad patterns, and design principle violations against what was planned in issue files. Use after implementation to verify architectural faithfulness and code quality.

Audits issue files for non-functional requirement gaps including security vulnerabilities, performance concerns, maintainability issues, and technical debt risks. Use when reviewing issue specifications for NFR completeness before implementation.

Reviews implemented code for security vulnerabilities, performance issues, maintainability concerns, and technical debt against what was planned in issue files. Use after implementation to verify NFR compliance and code quality.

Audits issue files for project structure violations, misplaced domain logic, incorrect file placement, naming convention breaches, and unfaithful area-based architecture adherence. Use when reviewing issue specifications for structural correctness before implementation.

Unified workspace management covering issue decomposition, workspace structure, tracker metadata, and eval infrastructure. Use when breaking down work into issues, creating issue hierarchies (epics/stories/sub-tasks), sizing work for agent execution, selecting issue templates, structuring any project management artifact, setting up a workspace, creating or managing any workspace entity, recording decisions or meetings, understanding workspace conventions, working with wikilinks and frontmatter, setting up tracker integration, syncing tracker data, looking up teams/labels/statuses/projects, creating issues that need tracker metadata, configuring a project management tool connection, or creating, managing, or running deterministic evals. Always use this skill when the user mentions issues, decomposition, epics, stories, sub-tasks, issue templates, project management, workspace structure, specs, features, abilities, scenarios, context, actors, concepts, memories, wikilinks, frontmatter conventions, tracker, Linear, GitHub Issues, Jira, labels, workflow statuses, teams, syncing project management data, or evals.