Delegation
- 8 installs
- 33 repo stars
- Updated April 26, 2026
- bighardperson/computer-science-skills-collection
Delegation is a skill that enforces an architecture-first workflow so AI-generated code fits an existing system before it is written.
About
This skill enforces an architecture-first workflow when delegating coding work to AI agents. Before any code is written, it requires the agent to read the architecture document, declare the target filepath, list dependencies and consumers, and check for conflicts. A developer uses it to keep AI-generated code consistent with an existing system and to run a completion checklist before marking work done.
- Architecture-first workflow for delegating projects to AI coding agents
- Forces filepath, dependency, and consumer declaration before code is written
- Ships a compliance checklist covering tests, types, lint, and validation
Delegation by the numbers
- 8 all-time installs (skills.sh)
- Ranked #12,269 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Jul 30, 2026 (Skillselion catalog sync)
delegation capabilities & compatibility
- Capabilities
- code review · architecture analysis · testing
- Use cases
- code review · refactoring · testing
What delegation says it does
Architecture-first workflow for delegating complex projects to AI coding agents. Ensures code fits the system before it's written.
npx skills add https://github.com/bighardperson/computer-science-skills-collection --skill delegationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8 |
|---|---|
| repo stars | ★ 33 |
| Last updated | April 26, 2026 |
| Repository | bighardperson/computer-science-skills-collection ↗ |
What it does
Delegate coding work to an AI agent while forcing architecture checks before any code is written.
Who is it for?
Delegating features to AI coding agents in a codebase with a strict architecture document.
When should I use this skill?
You are about to have an AI agent write code and want it to justify placement and dependencies first.
What you get
- architecture analysis
- filepath declaration
- production-ready typed code
By the numbers
- 11-item compliance checklist
- 5-step before-writing-code process
Files
Delegation
Architecture-first development where every line of code must justify its place in the system before it's written.
Context
You are the technical backbone of a production software system under active development. The codebase follows a strict architecture with zero tolerance for deviation. The architecture document is the single source of truth that prevents chaos.
Your mandate: Understand the architecture deeply, follow it religiously, and never generate code that violates its principles.
Before Writing Code
1. Read the architecture document — Understand where new code fits 2. State the target filepath — Declare before writing 3. List dependencies — What does this code import? 4. List consumers — What will use this code? 5. Check for conflicts — Does this duplicate existing functionality?
Response Format
Architecture Analysis
Read relevant architecture section and explain where new code fits in the system structure.
Filepath Declaration
📁 [exact filepath]
Purpose: [one-line description]
Depends on: [list of imports and dependencies]
Used by: [list of consumers/modules that will use this]Code Implementation
```[language] [fully typed, documented, production-ready code with error handling]
### Testing Requirements
- Tests needed: [describe unit tests and integration tests required]
- Test filepath: [matching test file location]
### Architectural Impact
⚠️ ARCHITECTURE UPDATE (if applicable)
- What: [describe any structural changes]
- Why: [justify the change]
- Impact: [explain consequences and affected modules]
## Compliance Checklist
Before marking code complete, verify:
- [ ] Input validation implemented
- [ ] Environment variables used for secrets
- [ ] Error handling covers edge cases
- [ ] Types enforce contracts
- [ ] Authentication patterns implemented
- [ ] Documentation updated
- [ ] Tests written
- [ ] Type check passes clean
- [ ] Linter passes clean
- [ ] Tests pass clean
- [ ] CHANGELOG is up to date
## Key Principles
1. **Maintain strict separation of concerns** — Frontend, backend, and shared layers stay separate
2. **Generate fully typed, production-ready code** — No partial implementations
3. **Follow established naming conventions** — camelCase for functions, PascalCase for components, kebab-case for files
4. **Identify conflicts immediately** — Ask for clarification before proceeding
5. **Never assume** — When requirements conflict with architecture, stop and ask
6. **Prefer existing patterns** — Don't create new solutions when patterns exist
## Related Skills
- Use `/frontend-design` for UI implementation
- Use `/senior-dev` for PR workflow after code is written
{
"ownerId": "kn780r0jztja96vfbt1wz9pas1808t9c",
"slug": "delegation",
"version": "0.1.0",
"publishedAt": 1770862527513
}{
"slug": "delegation",
"name": "Delegation",
"version": "0.1.0",
"installedAt": 1776152392219,
"source": "skillhub"
}Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10