Best for
- New feature development
- Code refactoring
- Architecture changes
Source profileQuality 89/100
archubbuck/workspace-architect/assets/skills/example-planner/SKILL.md
example-planner
Create detailed implementation plans for software features and refactoring tasks. Use this skill when planning new features, architectural changes, or major refactoring efforts.
- Source repository stars
- 17
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-05
- Source checked
- 2026-08-05
Decision brief
What it does—and where it fits
This is an example skill that demonstrates the Claude Skills format for workspace-architect.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/archubbuck/workspace-architect --skill "assets/skills/example-planner"Safe inspection promptEditorial
Inspect the Agent Skill "example-planner" from https://github.com/archubbuck/workspace-architect/blob/2e129d78b4f633bd7a10791e97961b2e4ae46754/assets/skills/example-planner/SKILL.md at commit 2e129d78b4f633bd7a10791e97961b2e4ae46754. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Instructions
When activated, follow these steps:
Gather RequirementsAsk clarifying questions about the feature or changeUnderstand constraints (time, resources, dependencies) - 02
Implementation Plan: User Authentication
Add OAuth 2.0 authentication to the application, supporting Google and GitHub providers.
Users can sign in with Google or GitHubSession management with JWT tokensLogout functionality - 03
Implementation Steps
1. Setup OAuth Providers (4 hours) - Register apps with Google/GitHub - Configure OAuth credentials - Store secrets securely
Setup OAuth Providers (4 hours)Register apps with Google/GitHubConfigure OAuth credentials - 04
Purpose
Use this skill when you need to create a comprehensive implementation plan for: - New feature development - Code refactoring - Architecture changes - Technical debt reduction
New feature developmentCode refactoringArchitecture changes
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 89/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 17 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- archubbuck/workspace-architect
- Skill path
- assets/skills/example-planner/SKILL.md
- Commit
- 2e129d78b4f633bd7a10791e97961b2e4ae46754
- License
- ISC
- Collected
- 2026-08-05
- Default branch
- main
View the original SKILL.md
Example Planner Skill
This is an example skill that demonstrates the Claude Skills format for workspace-architect.
Purpose
Use this skill when you need to create a comprehensive implementation plan for:
- New feature development
- Code refactoring
- Architecture changes
- Technical debt reduction
Instructions
When activated, follow these steps:
-
Gather Requirements
- Ask clarifying questions about the feature or change
- Understand constraints (time, resources, dependencies)
- Identify stakeholders and their needs
-
Analyze Current State
- Review existing codebase architecture
- Identify impacted components
- List technical dependencies
- Note potential risks
-
Design Solution
- Propose architectural approach
- Break down into implementable tasks
- Define acceptance criteria
- Estimate effort for each task
-
Create Implementation Plan Generate a plan with these sections:
Overview
- Brief summary of the feature/change
- Key objectives and goals
Requirements
- Functional requirements
- Non-functional requirements (performance, security, etc.)
- Constraints and dependencies
Architecture
- High-level design
- Component interactions
- Data flow
Implementation Steps
Detailed task breakdown with:
- Task description
- Dependencies
- Estimated effort
- Assignee (if known)
Testing Strategy
- Unit tests
- Integration tests
- E2E tests
- Performance tests
Risks and Mitigations
- Technical risks
- Timeline risks
- Dependency risks
- Mitigation strategies
Success Criteria
- How to measure completion
- Acceptance criteria
- Quality metrics
-
Review and Iterate
- Ask for feedback on the plan
- Refine based on input
- Update as requirements evolve
Best Practices
- Break large features into smaller, reviewable chunks
- Include time estimates (optimistic, realistic, pessimistic)
- Identify and document assumptions
- Consider backward compatibility
- Plan for rollback if needed
- Document decision rationale
Output Format
Use clear Markdown formatting with:
- Numbered lists for sequential steps
- Bullet points for parallel tasks
- Code blocks for technical details
- Tables for task breakdowns
- Diagrams (ASCII or Mermaid) when helpful
Example Output
# Implementation Plan: User Authentication
## Overview
Add OAuth 2.0 authentication to the application, supporting Google and GitHub providers.
## Requirements
### Functional
- Users can sign in with Google or GitHub
- Session management with JWT tokens
- Logout functionality
- Remember me option
### Non-Functional
- Response time < 2s for auth flow
- 99.9% uptime for auth service
- GDPR compliant data handling
## Implementation Steps
1. **Setup OAuth Providers** (4 hours)
- Register apps with Google/GitHub
- Configure OAuth credentials
- Store secrets securely
2. **Backend Implementation** (16 hours)
- Create OAuth callback endpoints
- Implement JWT token generation
- Add session middleware
- Write unit tests
3. **Frontend Implementation** (12 hours)
- Add login buttons
- Handle OAuth redirects
- Store tokens securely
- Implement logout
...
Related Resources
Notes
- Adjust detail level based on project size
- For small tasks, a lightweight plan is sufficient
- For large projects, consider creating ADRs for major decisions
- Keep the plan as a living document, updated as work progresses