Scaffold and govern the workspace/ directory — gitignored user interaction layer with dated session folders, task bridges, and estandares. Constitution XVIII + Workspace. [EXPLICIT] Trigger: "workspace", "scaffold workspace", "session folder", "workspace governance", "estandares"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdtemplates/output.docx.mdtemplates/output.html"The repo stays clean; the workspace stays flexible."
Scaffolds and maintains the workspace/ directory — the user's local interaction layer that is gitignored. Creates dated session folders, task bridges (connecting tasklog.md to working files), and manages the estandares/ reference area. Ensures workspace structure is canonical and never pollutes the version-controlled repository. [EXPLICIT]
workspace/ exists at project rootworkspace/ is in .gitignoretasklog.md for open items that need working directoriesworkspace/tasks/TL-XXX-<slug>/ directoriesworkspace/
README.md
tasks/
README.md
estandares/
README.md
workspace/YYYY-MM-DD-<slug>/
README.md
inputs/
outputs/
annexes/
workspace/tasks/TL-XXX-<slug>/
README.md
workspace/ to .gitignore if not presentworkspace/ is in .gitignoreYYYY-MM-DD-<slug> format| Anti-Pattern | Why It's Bad | Do This Instead |
|---|---|---|
| Committing workspace files | Pollutes repo with transient data | Keep workspace/ in .gitignore |
| Session folders without README | Lose context of what the session was for | Always add README with purpose |
| No task bridges | Disconnect between tracking and files | Create TL-XXX-slug/ per open task |
| Never cleaning up | Disk bloat, stale confusion | Review >30 day sessions |
session-protocol — Creates session folders as part of inittasklog-management — Tasklog items drive task bridge creationindexability-validator — Workspace READMEs follow same rulesrepository-organization — Workspace complements repo organizationExample invocations:
| Scenario | Handling |
|---|---|
| Empty or minimal input | Request clarification before proceeding |
| Conflicting requirements | Flag conflicts explicitly, propose resolution |
| Out-of-scope request | Redirect to appropriate skill or escalate |
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.