SkillFlux

    ↑ ↓ select↵ openSearch all of SkillFlux
    Browse directory
    Aspectmattpocock/skillsSuperpowers (obra)
    Main purposeTurn requirements interviews into specifications, task dependencies and code reviewsPlanning, debugging and testing workflows
    Source typeOpen-source repos · Open-source skill repositoryOpen-source repos · Open-source skill repository
    Use casesCoding & development, Planning & long tasks, Content & writingCoding & development, Planning & long tasks, Security & review
    LanguageEnglishEnglish
    PricingFreeFree
    Best forDevelopers who need to clarify hidden assumptions, acceptance criteria and project vocabulary before implementation. Teams with specifications or tickets that want to implement in dependency order and distinguish coding standards from requirement coverage.Teams bringing planning, debugging and testing into a shared development process. Developers willing to read the framework’s rules and adapt them to a project.
    LimitationsSome workflows require a configured issue tracker, domain glossary and architecture decisions. Implementation and review may also depend on other skills, Git and subagents. Interviews, specification publication and ticket approval have different interaction boundaries. The 38 skills are not one program that completes development in a single call; in-progress also contains workflows under development upstream.Framework rules may overlap with project conventions and need to be reconciled before adoption. Testing and review instructions are not themselves test results or security conclusions.
    SkillFlux sample40% clean · 0/20 fail at least one check · 12/20 do not say when to use the skill · 0/20 have no license we could find100% clean · 0/15 fail at least one check · 0/15 do not say when to use the skill · 0/15 have no license we could find

    mattpocock/skills: SkillFlux note

    This page analyzes the instructions, references and scripts of the 38 skills at a pinned commit, across engineering, productivity, misc and in-progress; it does not claim execution testing of these workflows. Listed skills each have a health check report; install them by following the original repository.

    Visit mattpocock/skills ↗

    Superpowers (obra): SkillFlux note

    Start with a change covered by existing tests and inspect the output of each step from planning to verification. The process should serve the project’s acceptance criteria. Explain adjustments where a step does not fit; completing a process is not proof that the feature works.

    Visit Superpowers (obra) ↗

    "Clean" is the share of sampled entries with no failing check, a "when to use" description and a license. Sampling reads files only and does not show whether a skill works. Method