Project workflow
Роли и базы знаний для агентов а также их менеджмент в виде текстовых файлов для использования с LLM.
npx -y skills add tikhomirovv/agents-knowledge --skill project-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Universal project workflows for software repos — brainstorm ideas, maintain docs, research and file backlog issues, implement with PR/MR. Works with GitHub and GitLab. Use when discussing features, exploring the codebase, creating or updating issues, writing documentation, or implementing tracked work.
SKILL.md
2.8 KB, as published. Nobody here has run it
Project Workflow
A set of independent workflows for common project work. Pick the workflow that matches the user's request — there is no required order.
User's explicit request always wins over heuristics below.
Platform
Detect from git remotes (git remote -v):
| Remote | CLI | Reference |
|---|---|---|
github.com | gh | platforms/github.md |
| GitLab host | glab | platforms/gitlab.md |
Read only the matching platform file before tracker or PR/MR commands. Discover flags via <cli> <command> --help.
Shared references
| File | Use |
|---|---|
| shared/orientation.md | Read before any workflow |
| shared/tracker-issues.md | Create, edit, blockers, labels (backlog + implementation comments) |
| shared/issue-template.md | Issue body structure |
Workflow router
| User signal | Workflow |
|---|---|
| brainstorm, explore ideas, think through options, PRD-level discussion | workflows/brainstorm.md |
update docs, README, .docs/, AGENTS.md | workflows/documentation.md |
| how does X work, problem, bug report, idea, tradeoffs, create/update issue, backlog, «answer only» | workflows/backlog.md |
| implement, fix, take issue #N, code changes, PR/MR | workflows/implementation.md |
If ambiguous, ask once which workflow fits.
Optional sequences (not mandatory)
Common paths — user may skip or reorder freely:
brainstorm → documentation → backlog → implementation
brainstorm → backlog → implementation
backlog → implementation
Examples:
- New product idea: brainstorm → capture in docs → backlog issues → implement
- Existing repo: backlog (research + file issue) → implementation
- Docs-only request: documentation only
Boundaries between workflows
| Workflow | Changes code? | Changes tracker? | Changes docs? |
|---|---|---|---|
| brainstorm | No | No | No (may recommend) |
| documentation | No | No | Yes |
| backlog | No | Yes (when asked) | No |
| implementation | Yes | Comments / state only | Only if issue requires |
Backlog creation and issue grooming belong to backlog, not implementation.