big-task
/big-task
Coordinate an engineering workflow when the user explicitly invokes big-task or requests an end-to-end engineering cycle. Choose planning, implementation, review, and verification depth from actual risk and stop at the requested deliverable. Ordinary features, file counts, and refactors do not trigger this lifecycle by themselves.
- Author
- xingfanxia ↗
- Repository
- ax-skills ↗
- Licence
- MIT
- Last repository change
- 16.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Coordinate an engineering workflow when the user explicitly invokes big-task or requests an end-to-end engineering cycle. Choose planning, implementation, review, and verification depth from actual risk and stop at the requested deliverable. Ordinary features, file counts, and refactors do not trigger this lifecycle by themselves.
Original author description
Coordinate an engineering workflow when the user explicitly invokes big-task or requests an end-to-end engineering cycle. Choose planning, implementation, review, and verification depth from actual risk and stop at the requested deliverable. Ordinary features, file counts, and refactors do not trigger this lifecycle by themselves.
How it works
- Scope and authority
- Establish the working contract
- Execute and verify
- Finish at the requested outcome
SKILL.md preview
--- name: big-task description: Coordinate an engineering workflow when the user explicitly invokes big-task or requests an end-to-end engineering cycle. Choose planning, implementation, review, and verification depth from actual risk and stop at the requested deliverable. Ordinary features, file counts, and refactors do not trigger this lifecycle by themselves. --- # Big Task Carry the requested engineering outcome through implementation and verification, using the lightest workflow that protects it. ## Scope and authority Read the user's request and standing project instructions together. Preserve accepted phases, acceptance criteria, existing authorization, and user-owned changes. A review or planning request remains read-only unless edits are requested. Invoking this router does not itself request commits, push, PRs, remote messages, merge, deployment, memory promotion, or repository cleanup. Continue authorized phases without asking again at each boundary. Resolve routine reversible choices using the repository's patterns. When a material choice cannot be inferred, prepare the concrete options and recommendation, ask once for the missing decision, and continue independent authorized work. Respect explicit sign-off gates; elapsed time or silence is not approval. ## Establish the working contract Inspect the applicable repository instructions, manifests, relevant source, tests, and supplied references. Identify the actual source of truth before editing generated files or copies. Keep the outcome, acceptance criteria, scope, verification, and material unknowns visible in a short plan. Reuse an existing plan; persist a new one only when dependencies or continuity need it. Choose depth from ambiguity, reversibility, blast radius, and user/data impact: | Work shape | Useful approach | |---|---| | Clear change following an established pattern | Implement directly and run focused checks. | | Several dependent deliverables | Keep an acceptance checklist and execute dependency order. | | Consequential architecture, persistence, concurrency, or public contract change | Resolve invariants and compatibility first; validate the risky path with focused evidence and specialist review when it adds confidence. | | Unproven feasibility or unclear product direction | Investigate the consequential uncertainty before expensive implementation. | File count, language, and the presence of a database do not determine process. Use [profile-detection](references/profile-detection.md) for unfamiliar repos and [routing-examples](references/routing-examples.md) for ambiguous work shapes. ## Execute and verify Own the bounded implementation end to end. Follow established patterns, make the requested behavior work, and update directly affected documentation when the change makes it inaccurate. Keep unrelated refactors and housekeeping out of the diff. Use bounded parallel agents when independent work can improve speed or quality and the environment permits delegation. Give each task explicit inputs, acceptance criteria, and file ownership. Keep coupled changes sequential; use isolated worktrees when shared state would conflict. Choose available capabilities and models from the actual task, without fixed role counts. Read returned evidence and integrate the result; delegation does not replace ownership or require another generic reviewer. Run checks that exercise the changed behavior and required repository contracts. Add regression tests where they protect a demonstrated failure mode. For visual changes, inspect rendered output against the relevant design reference; choose screens and states affected by the change. Reuse passing evidence until the diff or unresolved risk changes. Do not introduce coverage targets, test scaffolding, or repeated full-suite runs merely to satisfy this workflow. Use [review-discipline](references/review-discipline.md) for consequential review questions and [adaptation-hints](references/adaptation-hints.md) for migrations, UI references, or AI behavior. A broad audit or PR-fix loop runs only when it is part of the user's requested workflow. Each keeps its own scope and completion contract. ## Finish at the requested outcome All acceptance criteria must be implemented and supported by evidence, or identified as unresolved with the concrete blocker. A phase boundary is not a reason to stop while authorized work remains. A successful local build is not proof of deployment or PR approval. Honor authorized commit, push, PR, merge, and deployment phases when they are in scope; do not add them as a default ending. Use repository conventions for commit granularity and PR format. Remote review requests or bot messages need explicit authorization in the session. Report what changed, verification results, and material limitations with links to the deliverable. Use [report-templates](references/report-templates.md) only if a reporting format is useful. For explicitly requested cleanup, the [cleanup reference](references/phase4-8track-cleanup.md) provides removal checks; cleanup is not a final phase of ordinary implementation.
Files in this package (8)
- README.md 1 KB
- SKILL.md 5 KB
- references/adaptation-hints.md 1 KB
- references/phase4-8track-cleanup.md 2 KB
- references/profile-detection.md 1 KB
- references/report-templates.md 1 KB
- references/review-discipline.md 1 KB
- references/routing-examples.md 1 KB
Versions
The database has no other skills named big-task.
Database snapshot: 13.11.2026 · package version 6119710eb7c8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90may
Use when the user mentions MAY, requests an engineering team workflow, or asks for coordinated planning, implementation, review, and acceptance checks. - 100implement-feature
End-to-end feature implementation workflow. Use when the user says "implement", "build feature", "work on task", "start implementation", or any feature development work. Covers plan review, test writing, implementation, verification, and delivery. - 100autonomous-engineering
Run the continuous engineering orchestration workflow for deepseek-super-agent. Use when planning, delegating, implementing, reviewing, testing, merging, or resuming project development. - 90cycle
Run the full GoodReason workflow cycle (Strategist -> Architect -> Implementer -> Evolution) on a task. Use when tackling complex engineering tasks that benefit from structured analysis, design, implementation, and verification. - 90onegate-engineering
Evidence-driven, approval-gated engineering workflow for requirements, architecture, implementation, testing, security review and handoffs. Use when starting any engineering task in a repository. Implements 4-tier authorization gating. - 91engineering-os
Use for every task as your engineering operating system.