printpractical
- 12 skills
- 0 followers
- 1 day ago last updated
- ▌ Map · printpractical bundleUse on a brownfield codebase that needs a CONTEXT.md hierarchy. After intake, reverse-engineers the system and component architecture from existing code to produce root and component CONTEXT.md files. Use when that context would materially help; architect and triage do not require it. Also use when CONTEXT.md files are severely out of date.
- ▌ Plan · printpractical bundleUse after specify approval is approved to break confirmed outcomes into a traceable implementation checklist. Produces plan.md with sections, seam-firmness test labels, acceptance-criterion traceability, and one bounded review cycle without prescribing private control flow. Do not run unless the specify approval is approved.
- ▌ Idioms · printpractical bundleUse when language-specific implementation, interface, review, or refactor guidance is needed after the relevant language is known. Loads one applicable idioms pack rather than broad language guidance.
- ▌ Triage · printpractical bundleUse for bugs, small isolated fixes, or tiny changes that don't warrant the full architect→specify→plan→implement pipeline. Runs the direct implement→archive-ready lifecycle with implement and docs approvals, and escalates to architect if scope is larger than expected.
- ▌ Verify · printpractical bundleUse to reconcile CONTEXT.md files with the current state of the code. Detects drift using provenance stamps, classifies divergences by seam firmness, auto-updates soft prose to match code, and surfaces firm divergences for human adjudication. Use after hotfixes, drive-by PRs, or periodically to keep docs honest. Also the tool that runs during implement's docs reconciliation phase.
- ▌ Reforge · printpractical bundleUse when you have a PoC or prototype and want to rebuild it as a production-quality system from scratch. Distills the functional intent and lessons learned from the prototype, discards the implementation, and produces a reforge-seed.md that seeds a greenfield architect session. Do NOT use to improve an existing production system — use architect for that.
- ▌ Specify · printpractical bundleUse after architect approval is approved to run the specification phase. Batches material decisions with recommendations, requires explicit confirmation of each, finalizes interface changes, then runs an adversarial implement-as-if dry run for unresolved blockers. Emits decisions.md and reconciles architecture.md. Do not run unless the architect approval is approved.
- ▌ Refactor · printpractical bundleUse for behavior-preserving refactors, cleanup, technical debt reduction, or code-quality audits across a named path, component, layer, package, or the whole stack. Audits first, requires explicit user selection, then executes small verified batches with an independent review. Routes behavior changes and firm-contract changes to architect.
- ▌ What Now · printpractical bundleUse when you are unsure what to do next in the agent-toolkit pipeline. Reads all active change manifests, interprets the current state, and tells you exactly what skill to run next and why. Also handles edge cases like kickbacks in progress, multiple concurrent changes, and epic child ordering. Invoke with phrases like "what now", "what should I do next", "where are we", or "what's the status".
- ▌ Architect · printpractical bundleUse when starting a new feature, designing a new project, or making a substantial architectural change to an existing codebase. Entry ramp and spine phase 1. Captures intake before scoped context discovery, then challenges deviations from idiomatic patterns, surfaces refactors as first-class decisions, and produces a validity-checked architecture.md. For epics, decomposes into child changes instead of a single architecture.md. Do NOT use for bugs or tiny changes — use triage instead.
- ▌ Implement · printpractical bundleUse after plan approval is approved to execute plan.md. Implements each section to a green baseline, then runs one bounded independent RV review and behavior-preserving remediation over the whole change before the implement approval. Enforces the firm-seam tripwire, logs kickbacks, and reconciles CONTEXT.md. Do not run unless the plan approval is approved.
- ▌ Brainstorm · printpractical bundleUse when an idea, problem, or possible solution is not formed enough to begin architect. Explores the problem and alternative approaches, challenges assumptions during convergence, and can produce an optional architect-seed.md handoff for a later architect session. Do NOT use once the change is ready for architectural decisions — use architect directly.