Absolute skill
Eleven skills for the development loop: interview and spec, TDD build, UI, docs and codebase maintenance
- 223 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Changes project code and upgrades dependencies
- Runs tests and build commands
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/absoluteDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Changes project code and upgrades dependencies
- Runs tests and build commands
This is third-party code. Review the repository files before installing.
What it does
The set has three groups. The one-time absolute-init interviews you, detects the stack and writes a config the other skills read. absolute-work drives the daily loop: interview, spec, a dependency-graphed task board and test-first execution in waves, with approval gates between phases; absolute-spec, absolute-ui, absolute-simplify and absolute-docs sit alongside. Five maintenance skills upgrade dependencies, scan for vulnerabilities, remove dead code, pay down lint and type debt and fix flaky tests. The skills never commit on their own.
Who it is for. For developers who want the agent to agree on design and plan before writing code.
Good fit when
- You need to take a task from a vague idea to verified code with checkpoints
- You need a spec to discuss without implementation
- You need to upgrade dependencies or fix flaky tests
Not a fit when
- A small fix where an interview and a spec are overkill
- Your team already has a planning process that conflicts with the skill's phases
Example request
/absolute-work Add Google and GitHub login, interview me about requirements firstLimitations
The skills are in English and target agents that support SKILL.md. The full absolute-work loop has many steps and confirmations, which raises token use. The skills run the project's tests and commands. The README install command points to repositories that do not exist, so installation is manual from the main repository.
How to disable. Delete the absolute-* folders from the agent's skills directory.
FAQ
Can I install only some skills?
Yes, each skill installs separately; only the absolute-init config is shared.
Does the skill commit changes?
No, the skills write files and reports; committing is up to you.
Discussion
No questions or reviews yet.
Related
SkillsAn evidence-first development skill: the agent wraps code in a spec and a gauntlet of checks so line-by-line review becomes optional
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Standalone skills for the whole development lifecycle: product, architecture, planning, implementation, QA, delivery and operations
Two skills for spec-driven development: /spec asks questions and saves a document to specs/, /spec-impl implements an approved spec step by step
Kiro-style spec-driven development: a skill set that takes work from idea through requirements and design to autonomous implementation
A set of Claude Code skills for the dev workflow: worktree isolation, a service layer, evidence and review
README in short
The README explains which agent problems the set addresses and describes eleven skills by group: setup, daily loop and maintenance. It shows the absolute-work phases with gates and the .absolute-work/board.md state file. Installation uses npx skills add with flags for global install, agent selection and non-interactive mode. MIT licensed.
README badge
Original SKILL.md
--- name: absolute-work version: 0.5.0 description: > End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations. Triggers on "absolute work", "build this end-to-end", "plan and build", "break this into tasks", "grill me on this plan", "pick up this ticket", "run this migration". category: workflow tags: - workflow - sdlc - planning - tdd - spec - specification platforms: - claude-code - gemini-cli - openai-codex - mcp user-invocable: true argument-hint: "[target]" license: MIT maintainers: - github: maddhruv --- ## Absolute Work: End-to-End AI Development Lifecycle Absolute Work takes any unit of work — a ticket, a task, a plan, a migration — from fuzzy intent to verified code. It is one continuous skill with **hard gates** between phases: brainstorm a shared design, write and review a spec, decompose into a dependency-graphed task board, then peel tasks off **one safe wave at a time** with test-first verification. Nothing is assumed, nothing is silently expanded, and no code is written until the design is approved. The lifecycle has 6 phases: **INTAKE & BRAINSTORM → SPEC → DECOMPOSE & PLAN → EXECUTE → VERIFY → CONVERGE**