adol1111
- 15 skills
- 0 followers
- 6 hours ago last updated
- ▌ Task Preparation · adol1111 bundlePrepares one selected concrete task for implementation through task-local spec, optional plan, review pauses, and execution handoff. Use when roadmap state is confirmed and the next work is task-local preparation.
- ▌ Task Spec Execution · adol1111 bundleUse when older prompts, installed workflows, or tests still refer to task-spec-execution and need a compatibility redirect into the split task-preparation or task-execution-simple stages.
- ▌ Task Execution Simple · adol1111 bundleExecutes one prepared task through isolation, implementation, verification, review, and branch closing. Use when task-local docs are complete and the next work is straightforward direct execution.
- ▌ Planning Clarification · adol1111 bundleResolves roadmap-blocking planning ambiguity before roadmap decomposition. Use when goals, constraints, success criteria, or now-vs-later boundaries are unresolved by docs or prompt evidence.
- ▌ Doc Driven Spec Workflow · adol1111 bundleRoutes docs-driven repository work to the correct workflow stage and preserves handoff context. Use when the next step is unclear between bootstrap, clarification, roadmap planning, task preparation, or execution.
- ▌ Feature Spec · adol1111 bundleWrite or revise the durable behavioral contract for one explicitly targeted or unambiguously current Feature. Use when collaborators or execution agents need shared outcome, scope, observable rules, failure and compatibility behavior, and completion proof without relying on chat or prescribing implementation.
- ▌ Feature Close · adol1111 bundleVerify and close one completed Feature across its Task, Feature, and optional Milestone Acceptance records, then coordinate safe integration and cleanup without forcing a workflow.
- ▌ Task Planning · adol1111 bundleAdapt one explicitly targeted or unambiguously current agreed Feature into a user-confirmed graph of independent, agent-ready child Tasks. Use when a Feature is too large for one safe fresh context or spans people, agent windows, harnesses, or sessions and needs durable delivery boundaries, ownership surfaces, blockers, shared contracts, safe parallelism, or independently verifiable handoffs before implementation.
- ▌ Local Work Tracker · adol1111 bundleExplicitly initialize or operate a repository-local Feature owner index only when no external tracker exists. Use for local actor identity, Feature ownership, owner-filtered target discovery, Feature lifecycle transitions, and generated Feature views without making local tracking a dependency of other skills.
- ▌ Domain Context · adol1111 bundleMaintain durable domain terminology and qualifying architecture decisions in repository-local Markdown. Use when repeated or ambiguous terms need a shared glossary, or when a hard-to-reverse, surprising choice among genuine alternatives needs an ADR; do not use for temporary task discussion or ordinary implementation detail.
- ▌ Technical Design · adol1111 bundleDecide and document review-critical technical choices for one explicitly targeted or unambiguously current Feature or child Task when architecture, ownership, data, state, algorithm, concurrency, security, performance, or verification has materially different plausible approaches or a non-obvious invariant. Straightforward work needs no design artifact.
- ▌ Waypoint Workflow · adol1111 bundleRead repository evidence and recommend exactly one next standalone Waypoint or installed Matt Pocock skill for shared Milestone, Feature, Task, tracking, handoff, or implementation work. Use only when the user asks what to do next; never invoke the recommendation, mutate state, or chain stages.
- ▌ Milestone Planning · adol1111 bundleSelect or revise a shared Milestone as a frozen batch of owned Features from a requirement pool, and reconcile completed Features into a concise global history. Use for backlog scoring, shared iteration or release scope, Feature ownership, cross-Feature dependencies, exit coverage, completion indexing, or explicit Milestone replanning; never decompose Feature Tasks or drive implementation.
- ▌ Docs Workflow Bootstrap · adol1111 bundleExplicitly scaffold or adapt an optional repository-local Markdown convention for requirement and completion indexes, shared Milestones, Feature-owned specifications and designs, and nested child Task contracts. Use only when a team asks Waypoint to initialize human-readable engineering documentation without requiring local tracking or a fixed workflow.
- ▌ Implementation Plan · adol1111 bundleCreate or revise a durable implementation plan for one explicitly targeted or unambiguously current Feature or Task when the user wants to review execution before coding, work must remain recoverable across multiple meaningful slices or collaborators, or sequencing, migration, compatibility, rollout, rollback, or cross-module coordination creates real risk. Capture strategy, change map, stable slices, constraints, and final verification without prescribing commits.