A disciplined software development company powered by the Superpowers workflow — brainstorm, plan, build with TDD, review, and ship
An Agent Company based on Superpowers — an opinionated dev process with TDD, debugging, code review, git worktrees, and verification skills
This is an Agent Company package from Paperclip
| Content | Count |
|---|---|
| Agents | 4 |
| Skills | 14 |
| Agent | Role | Reports To |
|---|---|---|
| CEO | CEO | — |
| Code Reviewer | Engineer | ceo |
| Lead Engineer | Engineer | ceo |
| Release Engineer | Engineer | ceo |
| Skill | Description | Source |
|---|---|---|
| brainstorming | Explores user intent, requirements and design before implementation. Use before any creative work — creating features, building components, adding functionality, or modifying behavior. | github |
| dispatching-parallel-agents | Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | github |
| executing-plans | Use when you have a written implementation plan to execute in a separate session with review checkpoints | github |
| finishing-a-development-branch | Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup | github |
| receiving-code-review | Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable — requires technical rigor and verification, not performative agreement or blind implementation | github |
| requesting-code-review | Use when completing tasks, implementing major features, or before merging to verify work meets requirements | github |
| subagent-driven-development | Use when executing implementation plans with independent tasks in the current session | github |
| systematic-debugging | Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes | github |
| test-driven-development | Use when implementing any feature or bugfix, before writing implementation code | github |
| using-git-worktrees | Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification | github |
| using-superpowers | Use when starting any conversation — establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions | github |
| verification-before-completion | Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always | github |
| writing-plans | Use when you have a spec or requirements for a multi-step task, before touching code | github |
| writing-skills | Use when creating new skills, editing existing skills, or verifying skills work before deployment | github |
npx paperclipai company import this-github-url-or-folderSee Paperclip for more information.
Exported from Paperclip on 2026-03-23