existing task process
1. **Find the feature** — Locate the feature directory in `/docs/wip/`. If multiple WIP features exist, ask the user which one to work on.
Overview
Workflow: Continue WIP Feature
-
Find the feature — Locate the feature directory in
/docs/wip/. If multiple WIP features exist, ask the user which one to work on. -
Review progress — Read
tasks.mdto understand:- Which tasks are done, in-progress, or pending
- What dependencies exist between remaining tasks
- Any notes logged on previous subtasks
-
Review context — Read the linked
design.mdandimplementation.mdto understand the full picture. Also check any relevant contributing guidelines and documentation. Capy search: Searchkk:arch-decisionsandkk:project-conventionsfor context relevant to the feature being resumed. -
Detect active profiles — Apply shared-profile-detection.md. Unlike the fresh-idea flow, the feature directory's files ARE available: feed the full feature-directory file list (and any in-tree artifacts the feature has produced so far) to the shared procedure's file-based input model. If the file list yields no profile — common when the design is for future work that has not emitted profile-bearing artifacts yet — fall back to the design interaction pattern against the
design.mdprose; it iterates all profiles with## Design signalsand handles token matching + confirmation. For each active profile, use theReadtool on<plugin_root>/profiles/<name>/design/index.md— where<plugin_root>is the absolute plugin-root path you already know from SKILL.md context; skip silently if absent. Load every always-load entry; the profile'squestions.mdguides any further refinement and itssections.mdlists required sections the design document must cover. A design authored before the profile rubric existed should be audited againstsections.mdon resumption. -
Assess readiness:
- If tasks are well-documented and clear → proceed to implement using the
implementskill. - If tasks need refinement (missing details, unclear subtasks, gaps in the plan) → update
tasks.mdand/or the design/implementation docs before proceeding. Follow the documentation guidelines from the Ideas and Prototypes section.
- If tasks are well-documented and clear → proceed to implement using the