Assesses workspace alignment and suggests cleanup or realignment actions at key transition points.
Assesses workspace alignment and suggests cleanup actions at key transition points.
/plugin marketplace add jmagly/aiwg/plugin install utils@aiwgThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Assesses workspace alignment and suggests cleanup or realignment actions at key transition points.
This skill should be invoked:
checks:
- name: working_directory_size
description: Check if .aiwg/working/ has accumulated stale files
threshold: ">10 files or >1MB"
action: Suggest /workspace-prune-working
- name: orphan_drafts
description: Draft artifacts not linked to requirements
action: Suggest review or archival
- name: stale_locks
description: Lock files older than 24h
action: Suggest cleanup
checks:
- name: phase_documentation
description: Current phase docs match project state
sources:
- .aiwg/planning/phase-plan-*.md
- .aiwg/reports/*-completion-report.md
action: Suggest /workspace-realign if mismatched
- name: requirement_coverage
description: All requirements have linked artifacts
action: Suggest /check-traceability
- name: architecture_drift
description: Code diverged from documented architecture
action: Suggest architecture review or ADR update
checks:
- name: stale_artifacts
description: Key artifacts not updated in >30 days during active dev
artifacts:
- SAD (Software Architecture Document)
- Risk Register
- Test Strategy
action: Flag for review
- name: completion_markers
description: Artifacts marked complete but phase still active
action: Suggest status update
## Workspace Health Report
**Overall Status**: [Healthy | Needs Attention | Requires Realignment]
### Quick Actions
- [ ] Run `/workspace-prune-working` - 15 stale files in working/
- [ ] Review 3 orphaned draft artifacts
- [ ] Update risk register (last modified 45 days ago)
### Detailed Findings
#### Working Directory
- Status: Needs cleanup
- Files: 15 (threshold: 10)
- Oldest: inception-notes-draft.md (created 2024-11-15)
- Recommendation: Promote or archive before next phase
#### Documentation Alignment
- Phase: Construction
- Last phase report: Elaboration completion (2024-12-01)
- Missing: Construction kickoff documentation
- Recommendation: Run `/flow-elaboration-to-construction` completion steps
#### Traceability
- Requirements covered: 85%
- Orphan code files: 3
- Recommendation: Run `/check-traceability` for details
Add to flow command templates:
## Post-Completion
After this flow completes, consider running a workspace health check:
[workspace-health] Assessing workspace alignment...
If issues found, the skill will suggest appropriate cleanup commands.
The orchestrator should invoke this skill:
This skill should:
.aiwg/ structure/workspace-prune-working - Clean up working directory/workspace-realign - Reorganize documentation structure/workspace-reset - Full workspace reset (destructive)/project-status - Current project state/check-traceability - Verify requirement linksSearch, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.